Open MichelSuch opened 4 years ago
Could you please try this with NVDA 2019.3 Beta 1 Portable?
Some more information on this: The problem seems to come from a conflict with brxcom, the software that allows tu use the terminal's keyboard with no screen reader active. When brxcom is desinstalled, the display works fine, but only the display function, the keyboard remains inactive.
Oops, did not want to close this one!
This driver is pretty complicated and really needs a revisit. I wasn't able to test this with brxcom when I had a device available.
We really need a log with level debug, I think
Hi,
Here is the piece of log I got from the user, hope it can help, I paste it here because it is short.
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction (22:00:38.224) - MainThread (940):
registering pre_configSave action: <class 'brailleDisplayDrivers.papenmeier.BrailleDisplayDriver'>
DEBUGWARNING - brailleDisplayDrivers.papenmeier.BrailleDisplayDriver.connectBluetooth (22:00:38.535) - MainThread (940):
connectBluetooth failed
ERROR - braille.BrailleHandler.setDisplayByName (22:00:38.535) - MainThread (940):
Error initializing display driver papenmeier for kwargs {}
Traceback (most recent call last):
File "braille.pyc", line 1725, in setDisplayByName
File "brailleDisplayDrivers\papenmeier.pyc", line 306, in __init__
Exception: no device found
Please try to connect your Trio with usb. Do not install brxcom. That works as expected. Except braille input.
@MichelSuch are you still having this issue with NVDA 2024.2 or 2024.3 Beta?
Someone reports me that his Braillex Trio is not recognized under 2019.3. He tried connection in USB or Bluetooth and got the same result.
Steps to reproduce:
Connect a Braillex Trio to the PC, select it in the Braille Settings dialog.
Actual behavior:
After selecting the braille terminal, NVDA says it cannot load the braille driver (see log attached)
Expected behavior:
Should load
System configuration
NVDA installed/portable/running from source:
Installed or portable, same problem
NVDA version:
2019.3 and 2019.3.1
Windows version:
W10 64 bits
Name and version of other software in use when reproducing the issue:
Other information about your system:
Other questions
Does the issue still occur after restarting your PC?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
Works fine with 2019.2.1 nvda.log