KarsMulder
commented
2 years ago First, let's try the easy possible solution and test whether grabbing the input device solves the issue.
evsieve --input /dev/input/event0 grab --map key:f12 key:leftctrl key:c --print --outputRight now, the original input device is not grabbed, so whenever a key like "A" is pressed, two keyboards will appear to simultaneously emit the "A" event, and when F12 is pressed, one keyboard will emit F12 and the other will emit Ctrl+C. I am not sure how this could prevent the Ctrl+C from being received, but maybe it somehow does?
If that does not solve the problem, then this is probably related to issue #8, and the consequence of a in hindsight bad design decision. There is an EV_SYN type events which you do not see in the output of the --print line from evsieve, but can be seen if you use the third-party evtest utility to see which events your devices emit. The intent was for evsieve to handle these events automagically without having to ask the user about how to map those, and therefore the policy is "Whenever an EV_SYN event is read from any input device, send an EV_SYN to all output device which have received events since the last EV_SYN event."
Which means that the output of your virtual keyboard will look something like:
EV_SYN
EV_KEY KEY_LEFTCTRL 1
EV_KEY KEY_C 1
EV_SYNAnd the lack of an EV_SYN between the KEY_LEFTCTRL event and the KEY_C event causes some programs to misorder them.
As temporary workaround, you can try building evsieve from the main branch and then use the new --delay argument to delay the C key for a very short period to force an EV_SYN event to show up between the leftctrl and the C key:
evsieve --input /dev/input/event0 grab \
--map key:f12 key:leftctrl key:c \
--delay key:c period=0.000000001 \
--print \
--outputThis is of course not a very elegant solution. I could maybe add a clause like --output syn=always to always generate EV_SYN events between output events, but even if I did, it would be hard to document it in a way that an user could figure out they need that clause when they run into the same issue as you.
I wonder if it is worth breaking backwards compatibility and release an evsieve 2.0 that fixes this issue and a couple of other ones.
aggo15
I'm trying to use evsieve to map a single key and generate a combination key. For example, when I press
F12key, I want evsieve to outputCtrl+Ckey to my device.Here is the command I use
However, this command will not generate Ctrl+C key consistently. On the monitor of my device, it some time will output
^Cas expected, but most of the time I get[24~instead.Did I miss anything? Is there a way to achieve what I want?