Commit Graph

18 Commits

Author SHA1 Message Date
12dc2f75c7 Update README 2020-12-29 03:47:41 -03:00
3eaf2bddfe Update README 2020-12-29 03:46:32 -03:00
0c8326646a Expand mouse support
Until now mouse support existed just as side effect of muxing and that
mouse clicks are registered as key events. This expands the support for
mouse wheel and movement.
v0.3.1
2020-12-29 02:43:04 -03:00
5c7e6b5a5d Formatting 2020-12-28 23:35:47 -03:00
7428d959e0 Formatting 2020-12-28 23:31:58 -03:00
e5dc581ddf Formatting 2020-12-28 23:24:11 -03:00
41a2fa7f1e Rewrite in state machine look
- Also add new option to control internal delay of programmatic key
  sequences, when they're necessary.
v0.3.0
2020-12-28 23:13:34 -03:00
230f5c70d3 Update README v0.2.0 2020-12-28 18:49:00 -03:00
15636b64e7 Add help message and options
Solves #8 and !2
2020-12-28 18:37:50 -03:00
6ab17c7d1a Update README 2020-12-28 15:27:29 -03:00
220ca0bc71 Update README 2020-12-28 15:23:46 -03:00
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.
v0.1.3
2017-12-04 02:54:55 -02:00
0d88388a9e Add note about Ubuntu/Debian installation 2017-11-30 13:46:42 -02:00
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.
v0.1.2
2017-11-30 01:58:02 -02:00
27efcbbf96 Fix #4: Correctly follows evdev protocol
SYN events and different event timestamps are necessary for sending
sequential key events of the same key.
v0.1.1
2017-11-29 23:59:07 -02:00
6fa3ad14b3 Fix README build instructions 2017-11-24 13:33:03 -02:00
40137670a4 Fix link 2017-08-13 14:25:50 -03:00
60ce0b8cc5 Initial commit v0.1.0 2017-07-25 18:12:37 -03:00