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
Enable more braille keys via BRLTTY #6483
Comments
The issue here is finding good mappings for the BRLTTY commands, as they don't seem to map overly well. Are you a BRLTTY console user? Do you have some feeling as to what BRLTTY commands should map to what NVDA commands? P4 because this affects only a few users. |
cc: @bramd, @Andre9642 |
@gregjozk Are you still interested in getting this fixed? |
Hello,
right now, no, due to having a protocol converter, which successfully
converted my Satellite 44 to BC6 (enabled more or less all key
combinations except of status cells) but it was not a skope of this
issue.
however others, who are not so happy than me, mey benefitt from this
PR (see Narrator's documentation)
anyway thanks for your excelant work.
2020-04-28 19:32 GMT+02.00, Leonard de Ruijter <notifications@github.com>:
… @gregjozk Are you still interested in getting this fixed?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#6483 (comment)
|
Hi Folks, My Machine runs Linux and windows with nvda in a kvm based virtual machine. I think having brlpinput support over brltty could improve thing a bit :-). |
Hmm this is going to be very complex if you want to cover every braille display. I think the HID standard will replace this at some point. |
* Mark the BRLTTY braille display driver as thread safe * Improve availability check for BRLTTY braille display driver: only report as available if a named pipe for BrlAPI is present * Add more BRLTTY key bindings (nvaccess#6483): * learn: toggle NVDA input help * prefmenu: open the NVDA menu * prefload/prefsave: Load/save NVDA configuration * time: Show time * say_line: Speak the current line where the review cursor is located * say_below: Say all using review cursor
Partly related to issue #6483. Summary of the issue: The BRLTTY driver was available even when there was no BRLTTY instance with BrlAPI enabled running on the local computer (the only type of connection supported for now). Opening the actual connection has quite a long timeout, so this cannot be done as an availibility check. However, BrlAPI uses named pipes in a known location, so we can use that to check for availability. In the future we might also expose this as a port selection if multiple pipes are discovered and/or we add an interface to connect to a BrlAPI server on another host over TCP. While I was working on this driver, I also marked it threadSafe and added a few more keybindings. Description of user facing changes The BRLTTY driver will not show up in the list of braille displays if no local BRLTTY with BrlAPI enabled is running. More BRLTTY commands have been mapped to NVDA actions.
Currently users, who use BRLTTY as their display, can use only five of many commands. Is it possible to enable more of them?
Jožef
The text was updated successfully, but these errors were encountered: