not again

This commit is contained in:
sezanzeb 2020-11-18 13:22:04 +01:00
parent dc74b5ddb6
commit d2417500fb
2 changed files with 5 additions and 1 deletions

View File

@ -68,7 +68,8 @@ holding down a button that is mapped to shift will (would usually have
a keycode of 10, now triggers writing 50) write "!!!!!!!!!". Even though a keycode of 10, now triggers writing 50) write "!!!!!!!!!". Even though
no symbols are loaded for that button. no symbols are loaded for that button.
This is because the second device that starts writing an event.value of 2 will **The Sixth idea** continues with the fourth. The described problem is
because the second device that starts writing an event.value of 2 will
take control of what is happening. Following example: (KB = keyboard, take control of what is happening. Following example: (KB = keyboard,
example devices) example devices)
1. hold a on KB1: `a-1`, `a-2`, `a-2`, `a-2`, ... 1. hold a on KB1: `a-1`, `a-2`, `a-2`, `a-2`, ...

View File

@ -49,3 +49,6 @@ sudo python3 setup.py install && python3 tests/test.py
- [x] ask for administrator permissions using polkit - [x] ask for administrator permissions using polkit
- [ ] make it work on wayland - [ ] make it work on wayland
- [ ] add to the AUR, provide .deb and .appimage files - [ ] add to the AUR, provide .deb and .appimage files
Before you consider contributing to the evtest injection and xkb mechanics,
I need you to understand the stuff in HELP.md