Prevent crash when selecting papenmeier braille display driver, remove brxcom wrapper#13348
Conversation
BrxCom via wrapper dll removed. Wrapper was not compatible with Python 3 anymore.
|
This is my first pull request. |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Given that BrxCom wrapper is just a dll it cannot be incompatible with Python 3 and removing support for it, while certainly the easiest solution, may introduce its own regressions. Could you please share the exception you got when trying to use BrxCom with Python 3 version of NVDA - it would be much better to fix the code rather than remove it? |
|
BrxCom is deprecated, so we (F.H. Papenmeier) don't support it anymore. I work at F.H. Papenmeier as software engineer, I am responsible for the braille display software and it's drivers. |
|
Thanks @Stefan-Kliesch-FHP That is very helpful to know. Could you please update the description of this PR to mention that BrxCom is deprecated and therefore support for it is removed? Also please remove mentions of BrxCom from user_docs\enuserGuide.t2t |
|
@Stefan-Kliesch-FHP Great to have you on board here! I'm glad to review the driver later this week! |
|
@Stefan-Kliesch-FHP Could you also elaborate on the papenmeier_serial driver? Do you think it is still used, or is it obsolete? |
BrxCom removed from user guide.
|
@LeonarddeR I think only a very few user will use it with the old braille dispays. I never tested it via serial port. I tested the braille driver with a BRAILLEX EL40c, BRAILLEX Trio, BRAILLEX Live+. I removed the BrxCom from the english and german userGuide.t2t. |
seanbudd
left a comment
There was a problem hiding this comment.
Thanks for this PR @Stefan-Kliesch-FHP.
I've suggested 2 minor changes, I think this should be good to merge after these are fixed up, but I'll wait for @LeonarddeR to do the review he wants to do.
restored file
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
| Wenn Sie weitere Informationen oder Hilfe bezüglich NVDA benötigen, besuchen Sie bitte die NVDA-Homepage unter NVDA_URL. | ||
| Neben Ressourcen der Community und dem technischen Support finden Sie auch zusätzliche Dokumentationen. | ||
| Auf diesen Seiten werden Informationen und Ressourcen zur NVDA-Entwicklung ebenfalls bereitgestellt. | ||
|
|
There was a problem hiding this comment.
Please reintroduce this line - there should be no changes to the German documentation in this PR as it would introduce conflicts for translators.
There was a problem hiding this comment.
Is it fine now?
There was a problem hiding this comment.
I'm afraid it isn't. This should be just empty line not hyphen. Essentially when looking at the list of files modified by this PR German user guide should not be mentioned at all.
There was a problem hiding this comment.
So I restored it from nvaccess:master and it's gone from the "files changed" list!
|
|
||
| If BrxCom is installed, NVDA will use BrxCom. | ||
| BrxCom is a tool that allows keyboard input from the braille display to function independently from a screen reader. | ||
| Keyboard input is possible with the Trio and BRAILLEX Live models. |
There was a problem hiding this comment.
Just to make sure - since you've removed this line are you saying that braille input is supported with other devices as well?
There was a problem hiding this comment.
BrxCom is a kind of connection chain. BrxCom connects to the braille display and the screenreader connects to BrxCom.
All keyboard inputs are handled by BrxCom and not passed through to the screenreader. NVDA is able to handle the qwerty and the braille input itself. Other screenreaders also implemented this function, so BrxCom is not needed anymore.
See test results for failed build of commit 1908a760a6 |
restore de/userGuide.t2t from nvaccess:master
|
How did the bluetooth tests go? This looks ready to merge otherwise. |
|
Sorry, been very busy last week. I will test it, today or tomorrow. |
|
So I tested it immediately, but I had a problem with the "Build (for testing PR)" version. The settings dialog wasn't available. |
|
I encountered an other strange behavior. If there was a working bluetooth connection via NVDA and the BRAILLEX Live+ and I switch off the braille display, NVDA starts to act strange. After a few seconds it lags with keyboard inputs and GUI updates. And it's not recovering. I have to switch on the braille display again or end the NVDA task in the Task-Manager. I think it's due to the lost connection. |
|
Hello everyone, When I try to select the braille display via the main settings dialog I get thje following traceback:
This can't be caused by the papenmeier driver, so any ideas? |
|
How do we continue here? |
|
Hey @Stefan-Kliesch-FHP, To get rid of the issues with bluetooth, I'd suggest a more thorough rewrite of the driver that is more like the other native drivers (e.g. Handy Tech, Hims, Baum). In short, make use of the hwIo module to ensure asynchronous communication with the display. Unfortunately, the FTDI2 module is a bit of a show stopper here, since it doesn't support overlapped IO I believe. |
|
I noticed that the FTDI driver should support both D2XX and virtual COM port access. So if we can switch to the virtual COM port model somehow, that would be greatly preferred and bring the following benefits. Note that these things shouldn't be impossible with D2XX, it will just take much more research and effort to get it working:
|
…creen (#13384) Fix-up of PR #13242 Originally reported by @Stefan-Kliesch-FHP in #13348 Summary of the issue: getStartOnLogonScreen can fail with UnboundLocalError when the autostart key does not exist. Description of how this pull request fixes the issue: If we failed to open autostart key we no longer try to access it.
|
@LeonarddeR |
|
Hi @Stefan-Kliesch-FHP - Could you update the template to include a changelog entry on how this affects the user? |
Link to issue number:
None.
Summary of the issue:
BrxCom wrapper is not compatible with Python 3 anymore and causes NVDA to crash.
Furthermore BrxCom is deprecated and is no longer supported.
Description of how this pull request fixes the issue:
BrxCom support via wrapper dll removed from braille display driver.
Testing strategy:
Modified braille display driver tested via Developer Scratchpad.
Known issues with pull request:
None.
Change log entries:
Fixed a bug where selecting the Papenmeier Braille Display Driver caused NVDA to crash when BrxCom is installed.