-
-
Notifications
You must be signed in to change notification settings - Fork 632
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
Braille Display Driver Hedo Germany #1897
Comments
Comment 1 by sebastian.kruber@... on 2011-11-10 15:50 The keypress / keyrelease method is very different to the ProfiLine series, thus I wrote a completely new driver. |
Comment 2 by jteh on 2011-11-30 23:08
...
nit: This can be written more Pythonically as
...
The cells will already be padded up to numCells, so you just need to pad for status cells, rather than calculating the total length. This padding probably isn't documented. If it isn't, I'll update the code doc. :) The gesture map and gesture classes at the bottom are indented with spaces. Please convert these to tabs to match other NVDA code. It'd be great if you could provide a User Guide section for this display. See user_docs/en/userGuide.t2t. Just use the section I wrote for the other hedo display as a base. Feel free to just attach the new section, rather than the whole User Guide. Thanks again for your contributions. |
Attachment hedoMobilLine.py added by sebastian.kruber@... on 2011-12-01 10:28 |
Attachment userGuide.t2t added by sebastian.kruber@... on 2011-12-01 10:29 |
Comment 3 by sebastian.kruber@... on 2011-12-01 10:33 The suggested changes have been made. The key mapping is identicall to the ProfiLine, thus the entry in the helpfile is identicall to the entry for the ProfiLine... except the name for the display of course. |
Attachment userGuide.t2t.extracted.txt added by sebastian.kruber@... on 2011-12-01 10:33 |
Comment 4 by jteh on 2011-12-01 10:45 |
Reported by sebastian.kruber@... on 2011-11-10 15:47
A second braille display driver for hedo MobilLine USB
The other driver can be found here:
http://www.nvda-project.org/ticket/1863
The text was updated successfully, but these errors were encountered: