-
Notifications
You must be signed in to change notification settings - Fork 146
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
Input chords/combos with order #1004
Comments
This feels like something that could be implemented by this: #128 |
Yeah probably, that issue and the thoughts behind, to give tap-hold even more granular control, are great and well invested time. They should make this use case even more feasible. However, you'd still need a dedicated layer, or two for our example, so the config might get a bit bloated with empty layers and just one or two actions. Then, I find that input chords, if only two keys are used, are very similar to a tap-hold config with a layer but terser in syntax, but again less flexible in usage (I think they do not work on layers or do they?). Moreover, I assume they do not share the same behavior when looking at idling and the different tap-hold-behaviors. But once we talk about +3-key-combos we are in a different territory, so it's not trivial to find a good design which is easy to implement, to understand and to combine with other constructs at the same time. |
A custom tap-hold behaviour could add arbitrary logic, it could accommodate 3 presses and more. But perhaps another way that exists today is sequences: simulator. |
Though perhaps this variant might be better so that key repeat is not lost.. at least I think. I haven't tested it for real 😅 |
I'd very much second this, because then it becomes like typing One particularly enticing use case for me personally would be this: let's say I want to invert the number row to be able to type symbols like With that said, chords v2 rock anyway 🙃. |
Does |
It should work in theory, that's a good thought. |
As a matter of fact, @newsve, give this a shot: (defchordsv2-experimental
(2 3) (switch ((input-history real 3 1)) next break () prev break) 200 all-released ()
) It gets a bit hairy with chords of 3 already tho, as you have to process |
Is your feature request related to a problem? Please describe.
Feel free to move this to discussions if it is out of scope (since you are working on chord v2, I thought I drop it here):
When using AHK, I wrote a behavior that interpreted the order of chords, first our starting point:
When holding first 2, then pressing 3 and all in the very fluid roll-over motion, I would skip to the next song.
And when holding 3, then pressing 2, I went back to the previous song.
I did the same for navigation Chrome tabs (left and right and when used as a rolling motion go to tab 1 or to the last tab). I think not considering the order (as an option) might be a missed opportunity.
These combos are super satisfying, feel natural and work extremely well. Just try it yourself. They go fast into the muscle memory and you do them without thinking.
Describe the solution you'd like.
Syntax is up to you.
Describe alternatives you've considered.
You could create extra layers but this would get too cumbersome quickly and also stuff like consider idling make stuff even more complex.
Also fork and switch could be used, but it wouldn't be much better and again, idling wouldn't be considered.
Additional context
No response
The text was updated successfully, but these errors were encountered: