[nvda] Re: Improvements

Gene wrote:
I've looked a bit at the ticket site after seeing your suggestion. I'll register and send the items as tickets. Since I haven't done this before, I hope you will let me know if there are any problems in the procedures I use in creating a ticket once you see the results.
No worries. Trac (and most other issue tracking systems) can be a bit tricky to learn for new users, but you'll hopefully get the hang of it eventually.
For now, I have one question. On reading the documentation, it appears the person writing the ticket assigns a severity rating. Is that correct or is this assigned later by a project member who reviews it?
That is a matter of project policy. At this stage, I'd assign a severity yourself; we can always reassign it later. One person's idea of "major" is different to someone else's, though, so ultimately, we will probably adjust the severity after discussion.
My other question, which doesn't refer to tickets is whether I should continue to send these reports to the list as well. Is this needless duplication or do you want those on the list to review problems that are also sent as tickets?
There are two answers to this. First, we have been discussing having all Trac ticket updates sent to the nvda-dev list, similar to the way svn commits are currently sent there. This allows interested users to see what tickets are being filed/updated. Even without this, users can use rss to keep up to date with new tickets. It would therefore seem to be needless duplication to send them to the list as well. Having said that, if you feel a particular issue could benefit from discussion with other users on list in a less formal fashion, by all means, feel free to post. To summarise, post if you feel there is other discussion that isn't quite ready for the ticket yet, but don't post if it is just a duplicate of the ticket. Note that this is my personal opinion; I haven't bothered to run this by the rest of the dev team, so feel free to chime in, Mick/Peter. :)
I do have one general comment which is that the behavior of NVDA in the Outlook Express edit field be reviewed. At least on my machine, the behavior you indicate you expect, reading by sentences, doesn't determine what is read.
It seems like there is definitely something unintensionally odd going on here. Again, I'm not familiar with the OE code, but I do know that Mick has had a lot of trouble getting it to play nice. There are all sorts of problems with correctly calculating line offsets, etc., which means that NVDA's idea of the cursor in certain situations could well be incorrect. Btw, this is probably something that's not quite ready for a ticket, as we aren't quite sure of the actual problem. 

Jamie

--
James Teh
Email: jamie@xxxxxxxxxxx
WWW: http://www.jantrid.net/
MSN Messenger: jamie@xxxxxxxxxxx
Jabber: jteh@xxxxxxxxxx
Yahoo: jcs_teh
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open 
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda

Other related posts: