Link to issue number:

Closes #8108

Summary of the issue:

When adding a braille display gesture to a script using the input gestures dialog, the added gesture shows up along with the description of the current display. However, when changing the current braille display, the gesture added earlier always shows up with the currently active display, not with the display driver description the gesture identifier belongs to.

Description of how this pull request fixes the issue:

1. Updated braille._getDisplayDriver to accept an additional keyword argument, caseSensitive. If False, this function allows case insensitivity, in which case the source part of an identifier (e.g. "handytech" for the id "br(handytech):b1") can be used to find the handyTech BrailleDisplayDriver class.
2. updated braille.BrailleDisplayGesture.getDisplayTextForIdentifier to find the description of the display the identifier belongs to. This is pretty easy now we can parse braille display gesture identifiers using the braille.BrailleDisplayGesture.ID_PARTS_REGEX.

Testing performed:

• Added a gesture for the handy tech display. When selected no braille, the gesture still showed up as a gesture belonging to the handy tech driver.
• In gestures.ini, changed handytech into handytechf. The gesture now showed up as referring to "Unknown braille display driver"

Known issues with pull request:

None

Change log entry:

• Bug fixes
  • When manually assigning functions to gestures for a particular braille display, these gestures now always show up as being assigned to that display. Previously, they showed up as if they were assigned to the currently active display. (Input Gestures window shows the name of the last braille display, not the originally defined one #8108)