8000 Hold while `multi-tap` is undecided by jokesper · Pull Request #958 · kmonad/kmonad · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Hold while multi-tap is undecided #958

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

Merged
merged 1 commit into from
Feb 13, 2025
Merged

Conversation

jokesper
Copy link
Collaborator

Fixes #955.

If we merge #524 (or #914). We should change InputHook to InputHookPrio.
Furthermore this breaks the last button being held the same length the key is held (See this comment for details).
To fix this we could reimplement press using InputHookPrio or change #524 as suggested.

@jokesper jokesper merged commit 3801a78 into kmonad:master Feb 13, 2025
13 checks passed
@jokesper jokesper deleted the fix-955 branch February 13, 2025 22:07
jokesper added a commit to jokesper/kmonad that referenced this pull request Feb 24, 2025
We also cancel `multi-tap` on release but only while released.
This should fix `multi-tap` in a layer keeping it's definition
through layer-switch (see kmonad#954 for an equivalent issue for `stepped`).

Also note, this does not revert kmonad#958 or kmonad#974.
Effectively they overshot the goal slightly.
It also doesn't reintroduce the issues kmonad#958 and kmonad#974 where
designed to fix.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4C15
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Best way to achieve double tap without timeouts?
1 participant
0