-
-
Notifications
You must be signed in to change notification settings - Fork 654
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 doesn't work on last snapshot #17502
Comments
Hello. I cannot reproduce this with the Focus braille display. But I saw this behavior in a previous portable alpha version with an EcoBraille display. I fixed it with a workaround, that was to enable the braille viewer. |
I am on last alpha with a Brailliant BI40x and I cannot reproduce this issue. |
I am writing with nvda_snapshot_alpha-34750,8a82bd5b.exe as portable installation, braille display is caiku albatross 80. All seems to work normally. I have also updated installed version to current alpha at same laptop, and all seems to work normally as well. Os is w11 23h2. |
I confirm that if I activate the braille viewer, then I can use the display braille correctly. |
Cc: @bramd , @dkager , @LeonarddeR |
Hi, Is this happening if NVDA is told to show speech output in braille? If yes, I think we need to combine this issue with #17092 as the cause might be the same. Thanks. |
@dreinn are you still having this problem? Could we please get a full debug log? |
@dreinn are you sure alpha-34735,bdd31537 is the first snapshot to exhibit this behaviour? |
@SaschaCowley Oh no! At all! I can only say that on 2024.4 it works properly, but I really don't know from which snapshot there is this bug. |
@SaschaCowley I attach here a log file with add-on disabled and debug activated. |
@dreinn could you please post a new log after you enable following advanced logging options in NVDA advanced settings?
Thanks |
@SaschaCowley here it is. |
@dreinn Have you tried this with add-ons disabled? |
I think I know what the problem is. I will provide a possible fix. |
@LeonarddeR @SaschaCowley Hello, I don't run NVDA from source, so I can't test your fix until it will be included in a snapshot. |
I'm sorry @LeonarddeR First of all thank you for having made a snapshot so soon! |
@LeonarddeR I have an idea, i will replace the driver manually and each file which has to do with braille. |
Replacing the drivers won't work here. |
nope. Overwriting only the lilli.dll driver doesn't have any effect. So, in order I can test it, please commit your solution to the alpha snapshot system. |
I've started a try build which will be fully signed. I'll provide the
link when it is done.
|
yes! it works properly! |
Please do'nt close an issue that is under investigation/that has a pr attached that is not yet merged. Merging the pr will automatically close the issue. |
Steps to reproduce:
Start NVDA, select MDV Lilli display driver.
Actual behavior:
Expected behavior:
NVDA logs, crash dumps and other attachments:
This is what NVDA logs when I press a navigation key from the display braille:
ERROR - scriptHandler.executeScript (09:48:48.268) - MainThread (16984):
error executing script: <bound method GlobalCommands.script_braille_scrollForward of <globalCommands.GlobalCommands object at 0x07C918F0>> with gesture 'RG'
Traceback (most recent call last):
File "scriptHandler.pyc", line 300, in executeScript
File "globalCommands.pyc", line 4034, in script_braille_scrollForward
File "braille.pyc", line 2834, in scrollForward
File "braille.pyc", line 1995, in scrollForward
File "braille.pyc", line 1988, in _nextWindow
File "braille.pyc", line 1890, in _get_windowStartPos
File "braille.pyc", line 1880, in windowPosToBufferPos
ZeroDivisionError: integer division or modulo by zero
System configuration
NVDA portable:
NVDA version: alpha-34735,bdd31537 (2025.1.0.34735)
Windows version: Microsoft Windows [Versione 10.0.19045.4894]
Other questions
Does the issue still occur after restarting your computer? Yes.
Have you tried any other versions of NVDA? If so, please report their behaviors. Yes, it works on all version. 2025.1 seems not compatible.
The text was updated successfully, but these errors were encountered: