Skip to content
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

Papenmeier: Cannot load braille display error in next snapshots #3819

Closed
nvaccessAuto opened this issue Jan 27, 2014 · 3 comments
Closed

Papenmeier: Cannot load braille display error in next snapshots #3819

nvaccessAuto opened this issue Jan 27, 2014 · 3 comments

Comments

@nvaccessAuto
Copy link

Reported by nvdakor on 2014-01-27 10:27
Hi,
If you attempt to set a braille display to be used with NvDA in next snapshots (particularly January 2014 snapshots), log viewer outputs the following traceback:

ERROR - braille.getDisplayList (02:22:11):
Error while importing braille display driver papenmeier
Traceback (most recent call last):
  File "braille.pyc", line 316, in getDisplayList
  File "braille.pyc", line 308, in _getDisplayDriver
  File "brailleDisplayDrivers\papenmeier.pyc", line 17, in <module>
  File "ftdi2.pyc", line 56, in <module>
  File "ctypes\__init__.pyc", line 435, in __getattr__
  File "ctypes\__init__.pyc", line 365, in __init__
WindowsError: [126](Error) The specified module could not be found

Prior to this, Brailliant B/BI is reported as unavailable.

Steps to reproduce:

  1. Use recent next snapshots.
  2. Go to NVDA menu, select Preferences, then go to Braille Settings.
    Expected: the list of braille displays should show up with unavailable displays being excluded, as reported in the log viewer.
    Actual: the above traceback is recorded in the log viewer.

Question: was the 1271 branch merged into next? If so, this might be the side effect of merging the work from that branch; if not, it might be something to do with ftdi2 module (as noted from the traceback).
Thanks.
Blocked by #3712

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2014-01-27 11:00
The error always occurred if you don't have the FTDI dll on your system, but we weren't logging it until recently. It's harmless, but should be fixed nevertheless. See #3712.
Changes:
Added labels: duplicate
State: closed

@nvaccessAuto
Copy link
Author

Comment 2 by halim (in reply to comment 1) on 2014-01-28 08:09
Replying to jteh:

The error always occurred if you don't have the FTDI dll on your system, but we weren't logging it until recently. It's harmless, but should be fixed nevertheless. See #3712.

Yes, ACK. Have a look to 3712 which has a patch attached since dec 2013.

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2014-01-28 09:06
Err, so it does. Curse Trac for not notifying of attachments by email. :) Thanks. I'll review and commit soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants