Consecutive key presses

[pheerai]

Feature Proposal:

Allows to pass several key codes that will be executed after one another. To do this, blocks of key codes are separated using /.

To make the key codes more readable in the config, this also introduces white-space trimming, making it possible to give 29-20/46/46/12/30/32/50/23/49/28 as 29-20 / 46 / 46 / 12 / 30 / 32 / 50 / 23 / 49 / 28. A rewrite to using an array would be another option, but will break existing setups.

The delays are configurable, defaulting to 100ms. If not enough delay values are given, the last one is repeated.

I am a bit unsure about the location of the array helpers – they might even be provided by go somewhere, I am not that proficient with it – as well the pad handling. It is possible to reduce the cases here down to "no entry" vs. "some entry", using the padding function in both cases, but this might be less clear.

Any comment on these issues, as well as regarding naming conventions or any other concern, is really appreciated.

As for the motivation: I use this code on my setup, e.g. to interface with the browser. Issue Ctrl+t to open a new tab, wait until it is responsive (~150ms), then type some bookmark alias char by char with less delay between the events (20ms)

Thanks for this tool 👍

[muesli]

Nice, I like this! I do wonder however, if we shouldn't combine key-codes and delays somehow.

[pheerai]

I changed the code to implement your proposal:
The default delay is "immediately" now.
If delay is required, it should get appended after the keycodes like so:
9-20+200 / 46 / 46 / 12 … (resulting in a 200ms delay after the first key and no additional delay for all the others)

[muesli]

@pheerai Thanks, I think I like the syntax! Will review this asap!

[muesli]

Pushed a few minor cleanups. Thank you for your contribution, @pheerai! ❤️