<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - libinput handles mouse button remapping and button scrolling in the wrong order"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100042">100042</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>libinput handles mouse button remapping and button scrolling in the wrong order
</td>
</tr>
<tr>
<th>Product</th>
<td>Wayland
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>libinput
</td>
</tr>
<tr>
<th>Assignee</th>
<td>wayland-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>freeyourmind@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>