Hi Patrick, thanks for the infos. I'm afraid you're out of luck, it seems that this device would need vendor-/model-specific extensions in our HID-mouse driver. It only announces two "regular" buttons, so our driver won't look for more (what xinput shows as buttons 4 and 5 are mappings from "Z axis" values). No kind of button mapping will help. If it's a workaround for you, you might enable middle-button emulation in X.
On 05/14/2018 01:26 PM, Patrick Marchand wrote: > On 05/14, Ulf Brosziewski wrote: >> Would you mind to run >> $ xinput --test /dev/wsmouse >> in an X terminal, press each button once, grab the output, >> and post it here? > Output: > > motion a[0]=1364 a[1]=907 > button press 4 > button release 4 > motion a[0]=1365 > motion a[0]=1367 > motion a[0]=1368 > motion a[0]=1370 > motion a[0]=1372 a[1]=906 > motion a[0]=1373 a[1]=905 > motion a[0]=1375 a[1]=904 > motion a[0]=1377 a[1]=903 > motion a[0]=1378 a[1]=902 > motion a[0]=1379 a[1]=901 > motion a[0]=1380 > motion a[0]=1381 a[1]=900 > motion a[0]=1382 > motion a[0]=1381 > motion a[0]=1380 > button press 5 > button release 5 > button press 5 > button release 5 > button press 5 > button release 5 > button press 1 > button release 1 > button press 3 > button release 3 > > So button 1 the left click > Button 3 is the right click > Motion is moving the ball > Button 4 and 5 are the scroll function on the ball > Clicking on the upper two button of the mouse does not register any events. >
