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.
It is TBD, whether I can use a held "modifier Button" (e.g., Button2) to create additional shortcuts from a given set of high-numbered mouse buttons.
Created attachment 7072 (I forgot the prerequisite misc.h change)
It is NOT necessary to include XInput2 extension. (Xproto, included by xlib, already provides those 'high-numbered' button events.
I Investigated the possibility of "mouse modifier button" usage (I.e., holding down a "modifier button" while clicking another) - the second click is processed within 'events.c', because the held button becomes trapped within some 'click-and-drag' code state. Even if the held button is high-numbered (e.g., Button10 AKA the "Task Button"), xfwm doesn't seem to notice that a different-numbered Button has been clicked "on top of" thei held button. That code is probably too hard for me, so I'll ignore that 'add-on' to the feature.
-- GitLab Migration Automatic Message -- This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/xfce/xfwm4/-/issues/256. Please create an account or use an existing account on one of our supported OAuth providers. If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev