Link to issue number:

Fixes #7713.

Summary of the issue:

When the Freedom Scientific driver is active, the input gestures dialog can't be launched in Master due to braille.BrailleDisplayGesture.getDisplayTextForIdentifier raising a ValueError. It turned out one of the identifiers in the freedomScientific driver was malformed, having the br(freedomscientific] prefix.

Description of how this pull request fixes the issue:

1. Fixed the malformed identifier in the freedomScientific driver
2. Provided a unit test that checks every display driver gesture map for possible malformed identifiers.
3. Added a keyword arg excludeNegativeChecks to braille.getDisplayList in order to list all braille display drivers, not only those that passed the check.
4. Stopped braille.BrailleDisplayGesture.getDisplayTextForIdentifier from raising a ValueError. instead, an error is logged and the identifier is returned with the prefix "malformed:"

Testing performed:

Ran the new unit test against the broken freedomScientific driver, it cached the mistake properly.

Known issues with pull request:

None

Change log entry:

• Bug fixes
  • Backward scrolling functionality has been fixed for freedom Scientific displays containing a left bumper bar. (Can't activate Input Gestures Dialog with Focus40 Blue Braille Display #7713)