-
Notifications
You must be signed in to change notification settings - Fork 21
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
Inconsistent send on release behavior? #153
Comments
I'm not on my computer to test this, but perhaps your intention was to have this instead? ShiftRight{Delete{!250ms}} >> Insert ^
ShiftRight{Delete} >> Delete ^ I believe this should send Having |
This unfortunately doesn't work. Insert is sent alone, so it would seem shift is required to be part of the output. It is also still only sent after shift is released, so that part of the problem remains the same. Also, the strange behavior remains (where Shift-Delete gets sent if you keep tapping Delete) |
Thanks for reporting. I could reproduce the strange behavior and will try to fix it. |
I kept trying and found a definition that works. It seems to behave perfectly no matter how I try to abuse it, and ShiftInsert is sent immediately after pressing Delete without needing to release Shift first.
The nonworking snippet copied from my first post:
The buggy behavior seems to be related to |
This slight variation from my original suggestion seems to work consistently as well:
|
What does it mean to nest the 250ms like that? The behavior seems the same with or without it, but maybe I'm missing something. |
The key preceding it is held down 250ms. |
In the following mapping pair, shift insert is sent after shift is released, but shift delete is sent after the timeout even while shift is held.
Other quirky behavior occurs if you hold shift and start tapping delete. At that point, Shift Delete is sent on every quick tap, even though that's Shift Insert's rule.
Generally messing around with pressing Shift Delete also leads to other odd behavior I wouldn't have predicted based on the rules here.
Here's my full config
The text was updated successfully, but these errors were encountered: