Attachment nvda.log added by criticview on 2008-10-26 22:26
Description:
the nvda error log

Comment 1 by jteh on 2008-10-26 22:59
The usage for review in NVDA will always be somewhat different to that of BRLTTY. Focus and review are two different "views" of the same information, but focus is almost always more limited than review. For example, in the command prompt, focus cannot move beyond the current line; i.e. you can't move there with the cursor keys. Console text editors are different, as they generally allow you to move to the previous or next line of text. Thus, to review text to which the focus cannot move, you need to tether the braille cursor to the review instead of the focus. You can currently toggle this with NVDA+control+t. Eventually, this will be possible from the display itself.

So, given this information, should we close this ticket as invalid or were you actually requesting something else?

Comment 2 by criticview (in reply to comment 1) on 2008-10-26 23:39
Replying to jteh:

The usage for review in NVDA will always be somewhat different to that of BRLTTY. Focus and review are two different "views" of the same information, but focus is almost always more limited than review. For example, in the command prompt, focus cannot move beyond the current line; i.e. you can't move there with the cursor keys. Console text editors are different, as they generally allow you to move to the previous or next line of text. Thus, to review text to which the focus cannot move, you need to tether the braille cursor to the review instead of the focus. You can currently toggle this with NVDA+control+t. Eventually, this will be possible from the display itself.

So, given this information, should we close this ticket as invalid or were you actually requesting something else?

This information did help a little. I can read the window after pressing ctrl +ins +t, but only using the left and right pan-keys. Prior and next line don't work. I also noticed that the lay-out changed when toggling between focus and review. If braille is tethered to focus, a lot (some times too much) info is displayed. If tethered to review, you only see the highlighted program in the start menu for excample.
Would it be possible to mix focus and review (for braille only) so that one can read the window content, return to the cursor-position with the press of one button, just like you would do with brltty under linux. This would reduce the need of speech feetback for some users, and come close to the way other "commercial" screen readers implement their braille support.

Comment 3 by jteh (in reply to comment 2) on 2008-10-27 00:34

This information did help a little. I can read the window after pressing ctrl +ins +t, but only using the left and right pan-keys. Prior and next line don't work.

Support for braille display keys other than scrolling and routing is not yet implemented.

I also noticed that the lay-out changed when toggling between focus and review. If braille is tethered to focus, a lot (some times too much) info is displayed.

This is the context of the focus.

If tethered to review, you only see the highlighted program in the start menu for excample.

IN the case of review, it doesn't make sense to show context because you can easily move to the parent object, etc. and you generally only want to review the current object. This is similar to speech, where we only speak changes in the context for focus.

Would it be possible to mix focus and review (for braille only) so that one can read the window content, return to the cursor-position with the press of one button, just like you would do with brltty under linux.

This would make it impossible to, for example, move the caret to the previous line with the braille display. Moving to the previous line would always switch to review. The advantage of having separate tethering modes is that you can dictate which cursor moves when you use commands on the display. Also, combining them means that there is no way to move the review cursor independently of the caret/focus; e.g. to review another object.

This would reduce the need of speech feetback for some users

I don't understand why this would reduce the need for speech feedback. Can you please explain?

and come close to the way other "commercial" screen readers implement their braille support.

Most commercial screen readers have at least two cursors and you can set the braille cursor to follow either one. It becomes even more confusing when you have a separate braille cursor because you then aren't moving any particular cursor at all.

Comment 4 by jteh on 2009-06-23 06:10
Changes:
Milestone changed from 0.6 to None

Comment 5 by mdcurran on 2011-01-28 05:01
To review the entire dos console, switch braille tethering to review with NVDA+control+t, and then use braille scrolling commands. Also note that with the addition of Input framework in 2011.1 this adds commands for scrolling by line for braille display drivers. Please see the relevant sections in the 2011.1 User Guide for a list of the new braille commands for each display.
Changes:
State: closed