4 ms·

How in the world is X supposed to know what USB event your mouse sends when you click the button on the side? Did you ask the mouse manufacturer for documentati

• dzaima 3y ago
  I don't know where that information comes from (I'd assume the kernel? wayland[0] refers to the kernel[1]), but surely if I, and every GUI app that wants to use the mouse, is supposed to know it, X definitely could too. If I recall correctly, the left/middle/right button values were documented (to 1/2/3, which doesn't match the linux header ones), so surely more could. [0]: https://wayland.app/protocols/wayland#wl_pointer:event:button https://wayland.app/protocols/wayland#wl_pointer:event:butto... [1]: https://github.com/torvalds/linux/blob/4a0fc73da97efd23a383ca839e6fe86410268f6b/include/uapi/linux/input-event-codes.h#L355-L363 https://github.com/torvalds/linux/blob/4a0fc73da97efd23a383c...
  • PH95VuimJjqBqy 3y ago
    I'm not sure I understand the complaint. Anytime I've ever had to map extra mouse buttons I've always had to do a discovery step to figure out what "button number" any specific mouse button mapped to.
    • dzaima 3y ago
      Is that for back/forward, or extra buttons on top of those? Back/forward have pretty standard meanings & usages so I'd expect them to work out of the box (and they have for me). Can't comment much on other extra buttons though, quite possible those don't really have a good way of being handled.
      • PH95VuimJjqBqy 3y ago
        I've never seen forward/back buttons that didn't involve the driver making interpretations.