[nvda] Re: Improvements
- From: "Gene" <gsasner@xxxxxxxxx>
- To: <nvda@xxxxxxxxxxxxx>
- Date: Fri, 30 Nov 2007 18:37:03 -0600
Janes
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. 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?
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?
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. I haven't clearly figured out how NVDA determines what it
should read but it appears to often be one or two paragraphs behind where
one is located in the composing edit field when using read to end. Also,
when moving around in the compose edit field,
read current line doesn't track properly. When I first started a reply to
this message, it remained in the subject line. Later, when I shift tabbed
to the subject line, then tabbed back to the message body, it did move to
the message body but was far behind my current location. In my very limited
testing, this problem appears to possibly be related to the read to end
problem. Read current line seems to remain at the first line of a paragraph
and it appears to coincide with where read to end starts to read when the
command is issued. A bit further testing before sending this message
reveals that read current line also doesn't stop at the current line. It
starts reading at the beginning of a paragraph and reads the entire rest of
the text.
Gene
----- Original Message -----
From: "James Teh" <jamie@xxxxxxxxxxx>
To: <nvda@xxxxxxxxxxxxx>
Sent: Friday, November 30, 2007 5:37 PM
Subject: [nvda] Re: Improvements
Gene wrote:
> I find that using review current line,
numpad 8, does not update as one repeats a search. The correct text is
moved to and can be read with the main keyboard arrow keys but using read
current line reads text from an old search.
This is due to the fact that I think NVDA only updates the review cursor
when NVDA thinks the user has moved the cursor; i.e. by pressing one of
the arrow keys, page up, page down, home or end. There are reasons we have
chosen not to update the review cursor when a caret movement event occurs,
but we may have to try to find an alternative, as I agree this is not
optimal.
While reviewing this message using NVDA, I found another problem. When
using read to end, reading always begins at the beginning of a paragraph
no matter where you are in the paragraph when using Outlook Express to
write a message.
According to my understanding of the code (which could be wrong, as I'm
not too familiar with the OE code), it should be reading by sentence. We
read by sentence here instead of reading by line because it is more
efficient. I think MSHTML edit controls behave rather badly in terms of
fetching lines, which is why we prefer to read by sentence here for a more
natural reading experience.
Btw, if you can, I'd encourage you to register an account on
trac.nvda-project.org and file tickets for these issues. I understand that
not everyone can do this, but it helps to make sure they don't just
disappear into the big void of forgetfulness. Of course, don't file a
ticket until you have a set of steps (or as near as possible) to reproduce
the bug. The first issue you reported is a good candidate for a ticket.
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
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
- Follow-Ups:
- [nvda] Re: Improvements
- From: James Teh
- References:
- [nvda] Improvements
- From: Gene
- [nvda] Re: Improvements
- From: James Teh
Other related posts:
- » [nvda] Improvements
- » [nvda] Re: Improvements
- » [nvda] Re: Improvements
- » [nvda] Re: Improvements
- » [nvda] Re: Improvements
- » [nvda] Re: Improvements
Gene wrote: > I find that using review current line,
numpad 8, does not update as one repeats a search. The correct text is moved to and can be read with the main keyboard arrow keys but using read current line reads text from an old search.This is due to the fact that I think NVDA only updates the review cursor when NVDA thinks the user has moved the cursor; i.e. by pressing one of the arrow keys, page up, page down, home or end. There are reasons we have chosen not to update the review cursor when a caret movement event occurs, but we may have to try to find an alternative, as I agree this is not optimal.
While reviewing this message using NVDA, I found another problem. When using read to end, reading always begins at the beginning of a paragraph no matter where you are in the paragraph when using Outlook Express to write a message.According to my understanding of the code (which could be wrong, as I'm not too familiar with the OE code), it should be reading by sentence. We read by sentence here instead of reading by line because it is more efficient. I think MSHTML edit controls behave rather badly in terms of fetching lines, which is why we prefer to read by sentence here for a more natural reading experience.
Btw, if you can, I'd encourage you to register an account on trac.nvda-project.org and file tickets for these issues. I understand that not everyone can do this, but it helps to make sure they don't just disappear into the big void of forgetfulness. Of course, don't file a ticket until you have a set of steps (or as near as possible) to reproduce the bug. The first issue you reported is a good candidate for a ticket.
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/nvdaThank 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
- [nvda] Re: Improvements
- From: James Teh
- [nvda] Improvements
- From: Gene
- [nvda] Re: Improvements
- From: James Teh