-
-
Notifications
You must be signed in to change notification settings - Fork 650
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI Automation in Windows Console: limit blank lines in review and initial word movement support #9647
Merged
Merged
UI Automation in Windows Console: limit blank lines in review and initial word movement support #9647
Changes from 13 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
41d4816
Restrict the number of blank lines shown in console UIA's object review.
codeofdusk 53ecca9
UIA console: only apply our custom move logic when not moving the caret.
codeofdusk a9575ba
Add basic word movement support.
codeofdusk 1cf0563
ConsoleUIATextInfo: support expantion by word.
codeofdusk 6083ded
consoleUIATextInfo._countCharsToEnd(reverse=True) is now consoleUIATe…
codeofdusk 768fe0f
Cleanup.
codeofdusk 9a8835c
Improve cursor placement after word movement.
codeofdusk bc55777
Review actions (without changes to expand)
codeofdusk 6f52524
Re-implement expand.
codeofdusk c2386b9
Review actions.
codeofdusk c016ab1
Merge branch 'master' into cmduia2-textinfos
codeofdusk 6557f04
Review actions.
codeofdusk 4e9bbe0
Review actions.
codeofdusk b12cbc9
Merge branch 'master' into cmduia2-textinfos
codeofdusk e4e96ef
Fix forward movement across lines.
codeofdusk d00a15b
UIAWinConsole support: Improve logic of moving previous word to no lo…
michaelDCurran 1df93fa
Merge remote-tracking branch 'origin/pr9647_fixMovePreviousWord' into…
codeofdusk 9fef531
Style.
codeofdusk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Expand should use similar code to move. E.g.:
If unit is word, then use _getCurrentOffset and _getWordOffsets and manually move the start and end of the range to have it correctly bound the current word.
Then, there is no need to change what text is exposed as the textRange will be correct.
The advantage of this is there is less to track, it is easier to read, and most importantly, later comparisons or movements of this textInfo won't behave like it is expanded to line even though the text returned is word.
There may be a question around performance: but I'd like to see the code changed to my proposed way before we then consider if optimisations are needed at all.