Skip to content
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

Persistent modifiers on partial release of modifier combo. Fixes #74 #76

Closed
wants to merge 2 commits into from

Conversation

rbreaves
Copy link
Contributor

@rbreaves rbreaves commented May 1, 2020

Apparently this issue has existed going back to even May 2019, and my changes to the on release behavior of modifier keys had kept that original behavior. It has been resolved now by checking the actual key released against the possible modifiers to be released. Newly mapped modifiers are released separately (also known as missing modifiers in output.py).

Original commit 8c4fadb introduced the bug, while fixing similar modifier key behaviors.

More info in the thread. #74

@rbreaves rbreaves changed the title - Persistent modifiers on partial release of modifier combo. Fixes #74 Persistent modifiers on partial release of modifier combo. Fixes #74 May 3, 2020
@rbreaves
Copy link
Contributor Author

rbreaves commented May 15, 2020

Withdrawing these fixes as it appears to also break the modifier persistence. I may just work on creating a separate HK function and then resubmit a fix. This way the functionality of keeping a held modifiers in sync with the original modifier will not interfere with some users desires to emit shortcut keys instead of keeping them fully in sync with the original key press.

@rbreaves rbreaves closed this May 15, 2020
archlinux-github pushed a commit to archlinux/aur that referenced this pull request Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant