Added extended flag for navigation keys (Windows) #184
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.
This commit fixes a bug that occurs when simulating navigation keys in combination with Shift in Windows.
So far, it has not been possible to select text reliably using (Ctrl) + Shift + Navigation key. The result of this action was inconsistent and dependent on the state of the numlock. If numlock was on, Shift+RightArrow did not mark one letter, but moved the cursor. The reason for this is obvious from the sequence of keyboard messages that appear in the system queue.
The following code should cause 6 keyboard messages to appear in the Windows system message queue, but the system releases the Shift key while the navigation key is held down. If you are interested in the details, check out The effect of numLock & The effect of Shift
Message log from the low-level hook
Before:
After: