nvda

5adfbb21 - Add single-key bindings for the HumanWare Brailliant C-keys (#20366) (#20454)

Add single-key bindings for the HumanWare Brailliant C-keys (#20366) (#20454) Fixes #20366 Summary of the issue: On HumanWare Brailliant displays with C-keys (three keys on each side of the braille line, e.g. BI 32, BI 40, B 80, BI 20X, BI 40X), the C-keys have no function when pressed individually. Only multi-key combinations are bound (e.g. c1+c3+c4+c5 for the NVDA menu). Note: the issue originally also reported dot7/dot8 as unbound. That part was incorrect — as pointed out in review, dot7 and dot8 are handled by the braille input system (dot8: translate and enter, dot7: erase last cell), which I have confirmed on hardware using input help. The dot7/dot8 bindings have been removed from this PR; it now only covers the C-keys. Description of user facing changes New default bindings for the Brailliant C-keys: c1: move braille display to previous line c2: scroll braille display back c3: move braille display to next line c5: scroll braille display forward These are pure braille display navigation commands mirroring the thumb keys; they do not emulate keyboard keys and do not interact with braille input. The existing multi-key combinations are unchanged. c4 and c6 remain unbound and can be assigned via the Input Gestures dialog. Displays that do not have C-keys never emit these key codes, so they are unaffected. The User Guide C-key table is updated accordingly, and its heading now also mentions the BI 20X and BI 40X, which have the same C-keys. Description of developer facing changes None. Description of development approach Added the missing entries to the driver's gestureMap in source/brailleDisplayDrivers/brailliantB.py; no logic changes. Updated user_docs/en/userGuide.md and added a changelog entry in user_docs/en/changes.md. HumanWare's User Guide (v2.6, support.humanware.com/en-usa/support/brailliant_bi_x_series) describes c1/c2/c3/c5 as previous item / pan left / next item / pan right. I am not treating this as authoritative for NVDA's assignments — it only served as a hint for which navigation functions users of these displays might expect. I am happy to change the defaults if the team prefers a different scheme. I used AI assistance (Claude) while drafting this change. I have reviewed every line myself and manually tested the bindings on real hardware as described below.