-
-
Notifications
You must be signed in to change notification settings - Fork 627
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APH Refreshabraille 18 has braille input problems. #3541
Comments
Comment 1 by jteh on 2013-09-22 00:19 When braille input stops working, what do you hear if you press braille keys while in input help mode (NVDA+1)? |
Comment 2 by ianr on 2013-09-22 00:32 As you can see I press B1, then the stick up, then B1 again. |
Comment 3 by jteh on 2013-09-22 23:46 |
Comment 6 by jteh on 2015-06-16 07:09 |
Comment 7 by James Teh <jamie@... on 2015-06-16 07:16
|
Comment 8 by James Teh <jamie@... on 2015-06-16 07:17
Changes:
|
Comment 9 by jteh on 2015-06-16 07:25 Special thanks to APH for providing me with a Refreshabraille to test with. |
Comment 10 by James Teh <jamie@... on 2015-06-17 04:19
|
Comment 11 by James Teh <jamie@... on 2015-07-01 03:40
Changes:
|
…d, braille input no longer stops functioning after pressing another type of key on the display. When all keys for a group were released, a 0 was still being set in the keysDown dict for that group. However, when testing for braille input, we count the number of groups in keysDown, assuming that groups with no keys down are not present at all. To fix this, remove a group altogether when all keys are released. Re #3541.
…d, braille input no longer stops functioning after pressing another type of key on the display. Fixes #3541.
Reported by ianr on 2013-09-21 23:54
I am using the native NVDA braille driver labelled Baum/HumanWare/APH braille displays with an APH Refreshabraille 18.
Specifically I have noticed these 3 issues in NVDA 2013.2:
1 The braille input buttons stop working completely after the stick is moved up, down, left, right, or pressed, or any routing key is pressed, or the forward and back keys located on the left and right sides directly under the routing keys are pressed.
They can be fixed by entering the NVDA Braille settings dialog and pressing the OK button, but will stop working again any time you use the stick or routing keys.
2 Sometimes after pressing the buttons to output a computer braille g, meaning dots 1,2,4,5, the g will not be output, but next time I press any of the 6 braille input buttons the g will be output and the input key I just entered is ignored.
3 When pressing the bottom left most key on the display \7/ is output, and when pressing the bottom right most key \8/ is output.
This last item can probably be solved by manually mapping these keys to commands using the gestures.ini file.
I'll admit I am not overly familiar with braille input and am assisting a teacher of the blind and visually impaired.
So my apologies if I'm missing something obvious and there is some simple way to switch back into braille input mode.
My search of the APH documentation has so far not mentioned this.
Thanks in advance.
Blocking #2928, #3716
The text was updated successfully, but these errors were encountered: