Braille: fix auto-tether after moving mouse and using review commands, allow panning after review commands#13718
Merged
Conversation
…ew_currentWord, and review_currentCharacter
LeonarddeR
approved these changes
May 23, 2022
LeonarddeR
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for taking this.
seanbudd
approved these changes
May 24, 2022
Member
|
Thanks @rob-aph |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link to issue number:
Fixes #8682
Fixes #11519
Summary of the issue:
#8682: when using the read_currentLine, read_currentWord, and read_currentCharacter commands after the caret has been moved, it is impossible to pan the Braille display through the displayed content.
#11519: when moving the mouse with Mouse Tracking on (default) and Braille Tether set to Auto (default), using read_currentLine, read_currentWord, and read_currentCharacter speaks content under the mouse, but does not update the Braille display with the spoken content.
Description of how this pull request fixes the issue:
These three global review functions all call braille.handler.setTether early in their processing. braille.handler.setTether clears the display buffer, making it impossible to scroll through the displayed content. braille.handler.setTether also does not update the display, causing the problems discussed in #11519 -- tether flags are set properly, but the display does not change. A simple call to braille.handler.handleReviewMove in all three cases solves both of these issues.
Testing strategy:
In NVDA settings, be sure Enable mouse tracking is checked, and Tether Braille is set to Automatically.
Known issues with pull request:
None observed thus far.
Change log entries:
Bug fixes
When Braille is tethered automatically and the mouse is moved with Enable mouse tracking on, the Report current line in review, Report current word in review, and Report current character in review commands now update the Braille display with the spoken content.
It is now possible to pan the Braille display through content after use of the Report current line in review, Report current word in review, and Report current character in review commands.
Code Review Checklist: