papenmeier driver: Handle non-existence of FTDI dll

[nvaccessAuto]

Reported by jteh on 2013-12-11 21:37
On a system without the Papenmeier USB drivers installed (e.g. if a Papenmeier display was never connected), the FTDI dll won't exist. This causes ftdi2 to fail to import. The papenmeier driver should catch exceptions when importing ftdi2. It can then do one of two things if this failed:

1. Return False from the check method so that the driver won't be used.
2. Only disable USB so that Bluetooth still works. This is better because someone might pair a display via Bluetooth which they never connect via USB.

It'd be better if someone who owns a display can do this so that it can be tested properly.
Blocking #3819

[nvaccessAuto]

Comment 1 by halim on 2013-12-13 09:21
Yes, the driver should work with bluetooth connection only without installing usb drivers. I.ll post a patch soon.
Currently I don't have a Braillex Trio to test it.
Thx for reporting.

[nvaccessAuto]

Attachment patch added by halim on 2013-12-19 06:14
Description:

[nvaccessAuto]

Comment 3 by James Teh <jamie@... on 2014-01-31 04:37
In [a58c195]:

A Papenmeier braille display can now be used even if a Papenmeier display has never been connected via USB.

Re #3712.

[nvaccessAuto]

Comment 4 by James Teh <jamie@... on 2014-01-31 04:40
In [10a2a48]:

Merge branch 't3712' into next

Incubates #3712.

Changes:
Added labels: incubating

[nvaccessAuto]

Comment 5 by jteh on 2014-01-31 04:40
Changes:
Milestone changed from None to next

[nvaccessAuto]

Comment 6 by James Teh <jamie@... on 2014-02-14 06:03
In [a6fadcd]:

A Papenmeier braille display can now be used even if a Papenmeier display has never been connected via USB.

Fixes #3712.

Changes:
Removed labels: incubating
State: closed

[nvaccessAuto]

Comment 7 by jteh on 2014-02-14 06:05
Changes:
Milestone changed from next to 2014.1