feature-request: flavor "hold-on-large-overlap"
There is a flavor for hold-tap behaviour I'd like to have: "hold-on-large-overlap"
Example: Lets say we have key "&mybehaviour LSHIFT A" and key "&kp S".
I often happen to "roll keys", that is, I will type A down>S down>A up>S up regardless of wanting to type "S" or "as". But there is one difference: If I want to type a capital S, there will be a large overlap (in ms, as well as "in percentage of the time where S is down") that overlaps with the time where A is down. But if I want to type "as" the time where both keys are down will be quite small.
Ideally, there would be a free parameter "overlap-time-ms" and if the overlap is at least that time, then hold behaviour triggers.
I can try to implement that behaviour myself, can you point me into some direction what I would need to do?
I'm not sure how this differs in practice from the tap-preferred flavor + retro-tap.
- With a
key 1 down → key 2 down → key 1 up → key 2 upchain of events, the only way the hold onkey 1should be triggered if you are using thehold-preferredortap-unless-interruptedflavors. - You describe not always wanting to trigger the hold just because
key 2gets pressed. You want to check ifkey 1andkey 2have both been held foroverlap-time-ms. - ...But that means
key 1is already being held. Your overlap criteria meanskey 1must be held for at leastoverlap-time-msto trigger the hold anyway. So...why not cut out the middleman and just examine how longkey 1is held? - If the answer is "because I don't want to trigger a hold at all if
key 1is held for too long without any press ofkey 2"; that's why you would wantretro-tap. (And if I'm misunderstandingretro-tap...you might want to settapping-term-msto a shorter value.)
Is there something I've missed/can you describe an alternate scenario?