Skip to content

support high-numbered mouse buttons ("gamer mouse" devices).

Submitted by rickstockton@reno-computerhelp.com

Assigned to Olivier Fourdan @olivier

Link to original bug (#13474)

Description

Created attachment 7068 diff for support of "high-numbered" mouse buttons, with "Button10" implemented.

This bug is a separated 'clone' of bug 9879. I have made a ton of comments in that bug, which actually dealt with this one.

Within 9879, comment 2 asks to support use of "Button10" mouse button events as a workspace switcher. I'm creating THIS bug to support the high-numbered buttons which are often present on "Gamer" mouse devices.

That bug is left unresolved, to deal with the configurability of mouse button event assignments which are "hard-coded" within events.c


The following Mouse Button Press events can invoke various WM "actions", if additional event code is added on top of the attached patch:

"Button11" "Button12" "Button13" "Button14" "Button15"

Even Higher numbers might be possible, but I have tested only though "Button14".

The attached patch implements the single additional high-numbered button which was requested by that specific comment - (i.e., Workspace Switch) as an unconditional response to that button press. The only other code change within the diff is the #include for the header file <X11/extensions/XInput2.h>; which makes recognition of these 'high-numbered' button events possible.

Attachment 7068, "diff for support of "high-numbered" mouse buttons, with "Button10" implemented.":
high_button_patch_xfwm4.txt

Version: 4.12.0