Emulator

When I set the expression to tap(`Click 0`, 5, 3) it behaves as follows:

Clicking once starts a five second input window without triggering the input. Clicking a second time within that window has no visible effect (but increments the counter). Clicking a third time within the window triggers the input for as long as the click is held. Any following clicks are ignored until the end of the window.

When the window ends all clicks are forgotten whether the input was triggered or not (unless you're still holding the triggering click, which lasts until you release it). That means that clicking once, then a second time after 4 seconds, then twice more at 6 seconds won't trigger an input but instead start a new window with 2 clicks that ends 11 seconds after the original input and needs only one more click to trigger the input.

Does that match what you're seeing? Either way, those functions could definitely use some documentation in the UI.

Dentomologist wrote in #note-1:

When I set the expression to tap(`Click 0`, 5, 3) it behaves as follows:

Clicking once starts a five second input window without triggering the input. Clicking a second time within that window has no visible effect (but increments the counter). Clicking a third time within the window triggers the input for as long as the click is held. Any following clicks are ignored until the end of the window.

When the window ends all clicks are forgotten whether the input was triggered or not (unless you're still holding the triggering click, which lasts until you release it). That means that clicking once, then a second time after 4 seconds, then twice more at 6 seconds won't trigger an input but instead start a new window with 2 clicks that ends 11 seconds after the original input and needs only one more click to trigger the input.

Does that match what you're seeing? Either way, those functions could definitely use some documentation in the UI.

Hello and thank you for the quick response. If you do the formatting this way it actually does work. The issue is then, that the tooltip shows the wrong formatting required. Entering the tap function yields "expected arguments: tap (input, seconds, taps=2) which to me suggests that you should type (Click 0, 5, taps = 3) when instead it is as you say (Click 0, 5, 3). Adjusting the tooltip could be beneficial to remove this confusion. Overall, I agree that the extended hotkey section could use more documentation as it currently is very trial and error.