9 Commits

Author SHA1 Message Date
Francisco Lopes
5c7e6b5a5d
Formatting 2020-12-28 23:35:47 -03:00
Francisco Lopes
7428d959e0
Formatting 2020-12-28 23:31:58 -03:00
Francisco Lopes
e5dc581ddf
Formatting 2020-12-28 23:24:11 -03:00
Francisco Lopes
41a2fa7f1e
Rewrite in state machine look
- Also add new option to control internal delay of programmatic key
  sequences, when they're necessary.
2020-12-28 23:13:34 -03:00
Francisco Lopes
15636b64e7
Add help message and options
Solves #8 and !2
2020-12-28 18:37:50 -03:00
Francisco Lopes
bb09cd8d9a Discard MSC_SCAN events
Given that only EV_KEY events are being mapped, without their scancode
counterparts, we just drop all scancode events to avoid having to map
them too, to syncing it with the corresponding mapped keys. This is
expected to be harmless.
2017-12-04 02:54:55 -02:00
Francisco Lopes
9f353f96c6 Another evdev protocol infringement
Even though Peter Hutterer commented that it's not technically needed to
send SYN/delay when the sequence of events is of different keys, it
seems to be shown necessary to do so, otherwise events are dropped in
random situations.
2017-11-30 01:58:02 -02:00
Francisco Lopes
27efcbbf96 Fix #4: Correctly follows evdev protocol
SYN events and different event timestamps are necessary for sending
sequential key events of the same key.
2017-11-29 23:59:07 -02:00
Francisco Lopes
60ce0b8cc5 Initial commit 2017-07-25 18:12:37 -03:00