https://bugs.freedesktop.org/show_bug.cgi?id=100042
Bug ID: 100042
Summary: libinput handles mouse button remapping and button
scrolling in the wrong order
Product: Wayland
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: libinput
Assignee: [email protected]
Reporter: [email protected]
libinput 1.6.2 (which isn't a choice in Version above)
xf86-input-libinput 0.24.0
With button scrolling enabled by running:
xinput set-prop DEVICE "libinput Scroll Method Enabled" 0 0 1
xinput set-prop DEVICE "libinput Button Scrolling Button" 3
xinput will synthesize scrolling events (buttons 4 5 6 and 7) when the
scrolling button is held down and the pointer is moved.
With the appropriate command to remap buttons:
xinput --set-button-map DEVICE 1 2 3 8 9 10 11
xinput can remap buttons, in this case 4, 5, 6 and 7 are remapped to 8, 9, 10
and 11.
Unfortunately, the button remapping happens *after* the synthetic presses from
button scrolling are created. If all the commands listed above are run, then
holding the scrolling button and moving the pointer produces events for buttons
8, 9, 10, 11. This makes it impossible to use button scrolling along with
remapping the physical buttons.
Evdev had the more preferable behavior of not remapping the synthetic events
from its "Evdev Wheel Emulation", which allowed the physical 4, 5, 6 and 7
buttons to be mapped elsewhere while button scrolling could produce events for
4, 5, 6 and 7.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
wayland-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
