4 ms·

Extra buttons starting at 8 is due to the mouse wheel taking 4-7 (both horizonntal and vertical scrolling are represented as a button) https://www.x.org/releas

by accoil 3y ago

Extra buttons starting at 8 is due to the mouse wheel taking 4-7 (both horizonntal and vertical scrolling are represented as a button) https://www.x.org/releases/current/doc/man/man4/mousedrv.4.xhtml https://www.x.org/releases/current/doc/man/man4/mousedrv.4.x... """ Option "ButtonMapping" "N1 N2 [...]" Specifies how physical mouse buttons are mapped to logical buttons. Physical button 1 is mapped to logical button N1, physical button 2 to N2, and so forth. This enables the use of physical buttons that are obscured by ZAxisMapping. Default: "1 2 3 8 9 10 ...". """

dzaima 3y ago
Right, I had seen that 4-7 was scrolling, but that's still not describing which of the numbers greater than 7 will map to the back/forward buttons.
- accoil 3y ago
  Is there an actual standard for mice at that point? I.e. have mice manufacturers ever written down what signals are backwards/forwards? The Logitech G600 has 20 extra buttons, and no backwards/forwards button. I think it's more convention, as the applications are ultimately what are deciding to do with the mouse button. There's nothing to say that they could not put a context menu on the left click.
  - dzaima 3y ago
    In a sibling comment I noted wayland referencing some kernel values[0]; and I'd hope there would be some reasonable standard. I certainly didn't have to manually configure chrome & firefox for them to know which buttons on my mouse to map to previous/next page. Maybe the more exotic mouses would need some, but I'd still expect in such case that the user is able to say "ok this button is 'back'" to their DE, and not necessarily be forced to configure that for every single application individually. [0]: https://github.com/torvalds/linux/blob/4a0fc73da97efd23a383ca839e6fe86410268f6b/include/uapi/linux/input-event-codes.h#L355-L363 https://github.com/torvalds/linux/blob/4a0fc73da97efd23a383c...
    - accoil 3y ago
      Which is what the ButtonMapping config is for :) That said, I do think it would be nice to have written down that 8/9 are commonly used as backwards/forwards. They are just not explicitly backward/forward buttons though.

by accoil 3y ago

dzaima 3y ago

Right, I had seen that 4-7 was scrolling, but that's still not describing which of the numbers greater than 7 will map to the back/forward buttons.

accoil 3y ago
Is there an actual standard for mice at that point? I.e. have mice manufacturers ever written down what signals are backwards/forwards? The Logitech G600 has 20 extra buttons, and no backwards/forwards button. I think it's more convention, as the applications are ultimately what are deciding to do with the mouse button. There's nothing to say that they could not put a context menu on the left click.
- dzaima 3y ago
  In a sibling comment I noted wayland referencing some kernel values[0]; and I'd hope there would be some reasonable standard. I certainly didn't have to manually configure chrome & firefox for them to know which buttons on my mouse to map to previous/next page. Maybe the more exotic mouses would need some, but I'd still expect in such case that the user is able to say "ok this button is 'back'" to their DE, and not necessarily be forced to configure that for every single application individually. [0]: https://github.com/torvalds/linux/blob/4a0fc73da97efd23a383ca839e6fe86410268f6b/include/uapi/linux/input-event-codes.h#L355-L363 https://github.com/torvalds/linux/blob/4a0fc73da97efd23a383c...
  - accoil 3y ago
    Which is what the ButtonMapping config is for :) That said, I do think it would be nice to have written down that 8/9 are commonly used as backwards/forwards. They are just not explicitly backward/forward buttons though.