in reply to NV Access

@NVAccess Oh, uh... they don't let you go back, just like iOS, Android, and practically everything these days which is all sorts of nonsense, but I only have it as a HID-compliant display tangentially for work, and my primary display works without issue even though there's a missing dot. I'll do a before-and-after comparison when i have a chance. @zersiax
in reply to Florian

@twynn Thanks, this might be getting closer. Looking at our user guide, we just say: "The Brailliant BI and B series of displays from HumanWare, including the BI 14, BI 32, BI 20X, BI 40, BI 40X and B 80, are supported when connected via USB or bluetooth. If connecting via USB with the protocol set to HumanWare, you must first install the USB drivers provided by the manufacturer. USB drivers are not required if the protocol is set to OpenBraille" nvaccess.org/files/nvda/docume…
in reply to Timothy Wynn

Report submitted. We will see what they say in result. @NVAccess, do we already have an issue in NVDA about the keybinding issue? Granted the quick reference isn't accurate anyway, e.g., Space+1+3 is not Shift+Tab but rather Home, but I can definitely submit something about the Humanware connection inconsistencies between USB and Bluetooth wit the 2.4 update as needed.
in reply to Timothy Wynn

@NVAccess Update. Found it:
Issue: github.com/nvaccess/nvda/issue…
in reply to Florian

@NVAccess Via @simon, there's a fix out. I have not seen that posted on the Brailliant BI-X Users list hence me not knowing about it earlier.
Post: freelists.org/post/aphmantisch…
Firmware: humanware.s3.us-east-2.amazona…
in reply to Simon Jaeger

@simon I just tested and the fix works. I'd just install the new build and make sure that "HumanWare Brailliant BI/B series / BrailleNote Touch" shows up when connecting via Bluetooth rather than "Standard HID Braille Display" in NVDA's Select Braille Display dialog. I was never able to reproduce the input keys not registering, so @zersiax could probably speak better into that issue. @jessewienholts @NVAccess
in reply to Florian

@twynn @simon @jessewienholts Belatedly jumping back in to comment (probably for anyone else finding this thread) that NVDA 2024.4.2 should also fix this issue: nvaccess.org/post/nvda-2024-4-…