Give support to button holding lock

[CarlosEkisde]

It would be nice having an option which when switched on made that pressing a particular button would be equal to hold it for the virtual device, and when pressed again, it would be released. It would work for some usecases particularly disabled persons or just for convenience.

[sezanzeb]

This is really uncomfortable to use, but a macro can do it:

if_eq($mode, 1, e(EV_KEY, KEY_A, 0).set(mode, 0), e(EV_KEY, KEY_A, 1).set(mode, 1))

there should probably be

key_up(a) and key_down(a) to simplify it a bit

[sezanzeb]

implementing if_unreleased would help

if_unreleased(a, key_up(a), key_down(a))

but the naming of if_unreleased might be ambiguous, considering a fictional macro of if_held or similar, which might refer to a key being held down on the keyboard. But maybe not and it is perfectly valid.

would key_up and key_down be better than key_release and key_press? "pressing a key" might refer to a complete keystroke in common language, so press might not be the best choice.

TODO:

• key_up (like key, but injects one event of value 0) (easy to implement)
• key_down (like key, but injects one event of value 1) (easy to implement)
• if_held (if the physical key of the mapping is pressed down) (somewhat easy to implement)
• if_unreleased (if key-mapper injected or forwarded a KEY_A down event, but not yet one that releases it. By using the unreleased datastructure it might work. Does unreleased also keep track of unmapped/forwarded keys? I guess that would be wanted as well for this macro) (might be a little bit difficult to implement)

[sezanzeb]

similar: #382 (comment)

[sezanzeb]

added key_down and key_up:

if_eq(
    $mode,
    1,
    key_up(KEY_A).set(mode, 0),
    key_down(KEY_A).set(mode, 1)
)