|
|
@ -99,11 +99,17 @@ I assume this is because:
|
|
|
|
|
|
|
|
|
|
|
|
**Seventh, final solution** By grabbing the mouse device (EVIOCGRAB) this
|
|
|
|
**Seventh, final solution** By grabbing the mouse device (EVIOCGRAB) this
|
|
|
|
won't happen. Since this prevents all the keycodes from doing stuff, no
|
|
|
|
won't happen. Since this prevents all the keycodes from doing stuff, no
|
|
|
|
empty xkb symbols file is needed anymore.
|
|
|
|
empty xkb symbols file is needed anymore. If 10 is mapped to a, it will
|
|
|
|
|
|
|
|
figure out the keycode for a in the system configuration (via setxkbmap -pke)
|
|
|
|
|
|
|
|
and write it into a new device that has proper capabilities. So no xkb
|
|
|
|
|
|
|
|
configurations are needed at all anymore.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# How I would have liked it to be
|
|
|
|
# How I would have liked it to be
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This solution would have made the macro thing and mapping of mouse-clicks
|
|
|
|
|
|
|
|
impossible though.
|
|
|
|
|
|
|
|
|
|
|
|
setxkbmap -layout ~/.config/key-mapper/mouse -device 13
|
|
|
|
setxkbmap -layout ~/.config/key-mapper/mouse -device 13
|
|
|
|
|
|
|
|
|
|
|
|
config looks like:
|
|
|
|
config looks like:
|