Oh, man, you've got my vote on all of these. Seems like it's been you
and I pushing for braille fixes on this list, maybe that's just me. But
Yeah, I am having a LOT, in all caps, of trouble scrolling my handy tech
active braille manually through a document. Yes, it has the ATC feature,
but if I want to go line by line, WE isn't keeping the display scrolling
right. It's very frustrating.
I know that all those changes couldn't be made before the final release,
but at least look at the scrolling and hotkey issues? Please? I use
braille constantly.
On 12/6/2014 1:41 PM, Vaughan Dodd wrote:
Hello everyone.
Recognising that braile developments could be part of the commercial release
of version nine, I stil want to profile the need for enhancements to
Window-Eyes's braile support.
I have often commented on the braille features which need attention or
inclusion, but here now is the full list.
1. Include the option for direct contracted braile input.
2. Include a continuous or autoscroll mode.
3. Group the braille hot keys feature so that it has a similar
categorisation to the speech hot keys. Thus: braile hot keys for mouse,
screen, browse mode etc.
4. Layout the hot keys as a table, so that it becomes possible to navigate
by function, hot key label, assignments etc.
5. Correctly label display buttons for each supported device in the hot keys
aplication. For example: the Braille Edge's buttons are still described as
advance 1, advance 2 etc, when they are referred to by HIMS as f1, f2 etc.
The new Alva display does not have the five way touchpad, which is still
referred to in the Window-Eyes hot keys. With specific continued reference
to the Alva, capturing many of the keys does not work.
6. More clearly describe the extent to which each display is supported or
not supported. For example: What will Window-Eyes do with the Focus Blue
displays from Freedom Scientific. Although I like these displays, because
there is no commitment from Freedom Scientific to open up support to other
screen reader developers, I believe that a day might come when support from
AI Squared for the Focus range of displays could be removed. The
Window-Eyes user experience with the Focus displays is disappointing.
7. Include an ASCII code chart in the manual.
8. Include instructions for writing user definable tables.
9. If users wish to improve the extent to which braille input is
accomplished, provide instructions on how to do this.
I am still hopeful that at least some of these suggestions will be included
in the full release of version nine, and I encourage users to express
opinions on this topic.
It is clear to me that generally, beta two advances the cause of
Window-Eyes, but there is more work to do.
Vaughan.
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
