You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my current config,r is a tap-hold-next-release, and e is not.
Pshft Pe Rshft Re gives "E". Pshft Pr Rshft Rr gives "r".
I understand that I have to make a choice: either I must require my custom tap/hold modifers to be held until after the target key is released, or I need to lose the ability to roll and get both characters.
I can live with learning to not roll, for my custom modifiers.
But what I would like to keep, is the ability to roll when the modifier is control, alt, shift, super, and the target key is a tap-hold-next-release (r above).
Is there a way to let the rolling trigger the modified key for these, or is there a drawback that I don't see now?
This is actually a long standing issue. See #524.
I don't know why the PR is marked as Draft or if there are any problems with it (except that it's old and has merge conflicts). This was opened long before I started working on the project (as a contributor, I don't have any access rights).
That sounds good! I'd be happy to build and test this, if someone wants to rebase or merge in master for conflict resolution. I sadly don't have the ha-skills (pun) to resolve the conflicts.
In my current config,
r
is atap-hold-next-release
, ande
is not.Pshft Pe Rshft Re
gives "E".Pshft Pr Rshft Rr
gives "r".I understand that I have to make a choice: either I must require my custom tap/hold modifers to be held until after the target key is released, or I need to lose the ability to roll and get both characters.
I can live with learning to not roll, for my custom modifiers.
But what I would like to keep, is the ability to roll when the modifier is control, alt, shift, super, and the target key is a
tap-hold-next-release
(r
above).Is there a way to let the rolling trigger the modified key for these, or is there a drawback that I don't see now?
This is kind of related to #903
The text was updated successfully, but these errors were encountered: