Open fiveHourNap opened 2 years ago
Quoting https://github.com/sezanzeb/input-remapper/issues/49#issuecomment-831622386:
X/Wayland do their own key repeat, the kernel key repeats are filtered in libinput and would only affect a VT
I really wish there was someone who really knows GNOME internals who contributes to this project. There are so many problems with environments that I just don't understand at all.
issue description
I have a trackball and the gsetting for scroll wheel emulation only works if the input-remapper is not forwarding the device.
Expected behaviour on pressing and holding the button: moving the physical ball scrolls instead of moving the cursor
Observed behaviour: moving the ball moves the cursor
system info
OS: Linux Manjaro 21.2.4
Kernel: 5.15.25
DE: GNOME 41.4 WM: Mutter 41.4 Device of concern: ELECOM TrackBall Mouse HUGE TrackBall
known information
org.gnome.desktop.peripherals.trackball
has propertyscroll-wheel-emulation-button
set to 7evtest shows that the device transmits value 2 while the button is held and forwarding is off
without forwarding:
with forwarding on but no rule set:
with forwarding on and
hold(BTN_TASK)
bound on the button:with forwarding on and
hold(event(EV_KEY, BTN_TASK, 2))
bound on the button:evtest reports the same device ID
Input device ID: bus 0x3 vendor 0x56e product 0x10c version 0x111
Libinput info for the trackball:
I initially thought that this is related to #185, which is why I included all this info. But a deeper dig revealed that this is related to the transmission of the hold value. Which, according to the comments in the code is not being forwarded. But the event is not being generated on its own, so I think a transmission is necessary.