Progressive keyboard reports: report mods separately#26258
Open
tzarc wants to merge 3 commits into
Open
Conversation
drashna
approved these changes
Jun 13, 2026
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
2 participants
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.
Description
A branch I'd had sitting for a while, figured I should PR it.
Adds progressive reporting for 6KRO/NKRO such that if a key and a mod are added simultaneously, then the first report contains the mod and the second contains the modded key. Reverse when a modded key are released.
Was a fix for the whole Remote Desktop not reporting mods correctly scenario; been a long time since I used Windows so I'm not sure if it's still an issue... but it was working back then.
Timing is optional and configurable.
Types of Changes
Checklist