Implementation of Multi-stage Hold Actions (cumulative hold-duration triggers) and Passive "Watch" Mode (Non-blocking)

[AllStar112]

Hi,

I would like to suggest a few feature additions. I am not an active or professional programmer, so I do not understand if this can be done or not, but I hope you can consider it:

1. Multi-stage Hold
   Briefly, if (e.g.) A is pressed for 1 second, it outputs B; if 2 seconds, it outputs C; if 3 seconds, it outputs D. So, when pressing A for 3 seconds, it outputs B C D sequentially.

Hold A 1000ms >> B
Hold A 2000ms >> C
Hold A 3000ms >> D

Use Case (Text Selection):
I am trying to create a shortcut for word and line selection:

# Select word
CapsLock !250ms CapsLock >> Control{ArrowRight} ^ Control{Shift{ArrowLeft}}
# Select line
CapsLock !250ms CapsLock{250ms} >> Home ^ Shift{End} 
CapsLock >> CapsLock

This code is not perfect yet. It would be much more comfortable if, during the second hold of CapsLock, it immediately blocks 1 word followed by 1 line. This would feel much better because we know exactly when the change occurs. And since CapsLock isn't "killed," the second CapsLock must also be released. Maybe the code would look like this (if combined with the second feature request below):

# Select word
watch (CapsLock) !250ms watch (Hold CapsLock 10ms) >> Control{ArrowRight} ^ Control{Shift{ArrowLeft}}
# Select line
watch (CapsLock) !250ms watch (Hold Capslock 250ms) >> Home ^ Shift{End}

2. "Watch Mode" (Passive Listening)
   For example, with a code like:

Watch (A) !200ms B >> C

The output would be AC. There is a passthrough system, so it only "observes."

Maybe this could be replaced with A !200ms B >> AC, but it cannot be applied if using (Control) >> F13 or Control >> F13. Doing so "swallows" the Control key, making it impossible to create other shortcuts. Even if worked around with Control{Any} >> Control{Any}, it would still send a single Ctrl pulse.

Another example:

CapsLock !250ms CapsLock >> Control{ArrowRight} ^ Control{Shift{ArrowLeft}}
CapsLock >> CapsLock 

In this case, CapsLock will experience a delay.
There are actually many other issues that occur, but I have forgotten some and missed others.

Perhaps if there were built-in functions for "word block" or "line block," it would be very helpful.

Thank you.

[houmain]

Thanks for the input!

"Multi-stage Hold"

I fixed a thing in 5.6.0 to make this work with timeouts.
I tested it with this configuration. F2 selects the current word or when longer held the whole line:

in = F2
held = Virtual
timeout = 100ms
!held in{timeout} >> Control{ArrowRight} Control{Shift{ArrowLeft}} held
held in{timeout} >> Home Shift{End} ^
!in >> !held

"Watch Mode"

This is already available with input expressions starting with ?. I need to make this more obvious in the readme.
With the 5.6.0 release these may also contain timings, so this should work:
? A !200ms B >> C