Is there a way to make 'require-prior-idle' work with multiple simultaneous modifiers without having to activate them very slowly?

[gitraar]

I've been testing the recent 'require-prior-idle' feature and noticed that it seems to prevent using multiple modifiers at the same time.

Lets say I have the following configuration:

hrm_a (tap-hold-order $tap-repress-timeout $buffer-ms a ‹⎈ (require-prior-idle $prior-idle-ms))
hrm_s (tap-hold-order $tap-repress-timeout $buffer-ms s ‹⌥ (require-prior-idle $prior-idle-ms))
hrm_d (tap-hold-order $tap-repress-timeout $buffer-ms d ‹⌘ (require-prior-idle $prior-idle-ms))

All modifiers work as intended if used alone. However, if I try to use any combination of them together, the only way for them to work is by pressing and holding each one slowly, allowing for the prior-idle timer to elapse between each key. This is great for typing but doesn't really work when I need to use multiple modifiers.

Am I doing something wrong? Is there a way to circumvent this behavior without going back to using a typing layer?

Should require-prior-idle not trigger if the previously held but not released key is itself a tap-hold key (or maybe wait for the previous key to release and actually resolve to a tap before deciding to enter "typing mode" in those cases)?

Thanks for any input.

[gitraar]

After additional testing, it seems like "tap-hold-order" is the problem. It makes sense that 'tap-hold-order' is triggering taps because the modifiers are all pressed simultaneously, thus within the '$buffer-ms' timer.

Multiple simultaneous modifiers work with other tap-holds, although they feel somewhat inconsistent. I'll add more information if I find it.

[jtroo]

I think the inconsistency may be due to flaws in updating the prior idle tick counter. Thanks for testing, will take a look.

[jtroo]

#2021 is an attempted fix