Skip to content

Handy Tech: Correct Bluetooth name for Braille Star 40 and fix gesture identifiers when braille input is on#7785

Merged
michaelDCurran merged 3 commits into
nvaccess:masterfrom
BabbageCom:brailleStarFix
Nov 22, 2017
Merged

Handy Tech: Correct Bluetooth name for Braille Star 40 and fix gesture identifiers when braille input is on#7785
michaelDCurran merged 3 commits into
nvaccess:masterfrom
BabbageCom:brailleStarFix

Conversation

@LeonarddeR
Copy link
Copy Markdown
Collaborator

@LeonarddeR LeonarddeR commented Nov 20, 2017

Link to issue number:

None

Summary of the issue:

The new handy tech driver contained a wrong prefix for the Braille Star 40 braille display

Description of how this pull request fixes the issue:

@bramd fixed the prefix in his handytech-native branch. I created a new branch based on master and cherry-picked that commit. @bramd: For future work on the ht driver, it might be better to start with a new branch, based on master. :)

See also my comment below regarding the last minute fix for braille input gesture identifiers.

Change log entry:

Changes from rc1 to rc2:

  • It is again possible to connect to Handy Tech Braille Star 40 devices using bluetooth
  • Fixed an issue where overriding handy tech display gestures resulted into warnings about malformed input gesture identifiers.

@LeonarddeR
Copy link
Copy Markdown
Collaborator Author

@michaelDCurran: Please also merge this one into RC2 if possible, as it formally fixes a regression since 2017.3

@LeonarddeR LeonarddeR changed the title Correct Bluetooth name for Braille Star 40 Handy Tech: Correct Bluetooth name for Braille Star 40 and fix gesture identifiers when braille input is on Nov 20, 2017
@LeonarddeR
Copy link
Copy Markdown
Collaborator Author

Woops, another last minute fix. When braille input was on, malformed input gesture identifiers were generated. I caught this by checking the i/o log, I saw gestures like "br(handytech.modularevolution):" . That's right, without the ID. The identifiers will now be similar to braille input identifiers, e.g. br(handytech):dot1+dot2+dot7+space.

@bramd
Copy link
Copy Markdown
Contributor

bramd commented Nov 20, 2017 via email

@LeonarddeR
Copy link
Copy Markdown
Collaborator Author

@bramd commented on 20 nov. 2017 19:58 CET:

Strictly, your fix for gesture identifiers is not really a regression,
but it's a trivial fix and I would also gladly see it in 2017.4.

It is a bug, but it's not live threatening if not included.
I just discovered that the current code is still not a complete fix. Let me do a quick test in two hours and commit something with complete testing performed this time.

@LeonarddeR
Copy link
Copy Markdown
Collaborator Author

Tested with all the keys on a Modular Evolution 88, including the left and right triple action keys and the keypad block.

@michaelDCurran
Copy link
Copy Markdown
Member

For future reference, rc PRs should be based off of the RC branchh. However, as Master has not changed since, it is okay.

@michaelDCurran michaelDCurran merged commit f4d56a1 into nvaccess:master Nov 22, 2017
@nvaccessAuto nvaccessAuto added this to the 2017.4 milestone Nov 22, 2017
@LeonarddeR LeonarddeR added the BabbageWork Pull requests filed on behalf of Babbage B.V. label Oct 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

BabbageWork Pull requests filed on behalf of Babbage B.V. bug/regression

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants