[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #58 from Nate Graham --- We're open to improving the UX in the future to allow directly triggering exposed global actions, rather than just keyboard shortcuts. But that's an improvement for the existing feature, so I'd recommend that someone submit a new feature request Bugzilla ticket to track it. :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #57 from Bernd Steinhauser --- (In reply to miranda from comment #56) > (In reply to Bernd Steinhauser from comment #55) > > Yes, that works. It would still be a good thing if mouse buttons could be > > assigned directly, so you can avoid having to assign a key (combination) to > > that button. Personally, I think that it should not matter to the DE whether > > a button event was triggered by a mouse button and key presse or even a > > button press by a game controller. > > Apologies if I wasn't clear, that was in response to Nate - I agree with you > here. A workaround is just that, a workaround, meaning from my perspective > the feature request should still be open. I think it's ok if this one is closed, but as a mid- to long-term goal, it should still be on the list in my opinion. It might be helpful though to put that into a new feature request outlining the problems and goals more precisely. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #56 from mira...@mirandastreeter.com --- (In reply to Bernd Steinhauser from comment #55) > Yes, that works. It would still be a good thing if mouse buttons could be > assigned directly, so you can avoid having to assign a key (combination) to > that button. Personally, I think that it should not matter to the DE whether > a button event was triggered by a mouse button and key presse or even a > button press by a game controller. Apologies if I wasn't clear, that was in response to Nate - I agree with you here. A workaround is just that, a workaround, meaning from my perspective the feature request should still be open. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #55 from Bernd Steinhauser --- (In reply to miranda from comment #54) > Wouldn't binding a keyboard button to a mouse button, followed by an action > to a keyboard button, be considered a workaround? The original bug report > seems fairly clear. Yes, that works. It would still be a good thing if mouse buttons could be assigned directly, so you can avoid having to assign a key (combination) to that button. Personally, I think that it should not matter to the DE whether a button event was triggered by a mouse button and key presse or even a button press by a game controller. The current implementation works sufficiently to cover the needs of most, I guess, but there are limitations, e.g.: - Combining Modifiers with mouse buttons might not work, as most of the time you'd want to assign a key combination to the mouse button and not a single key stroke. e.g. you assign Meta+F1 to button 7, but then you can't use Meta+button 7 for other things. - The configuration is not device-specific. There surely are arguments pro and con this, but if you are using multiple mice, it might not make sense to assign button 7 to the same key combination on both devices, since they could be located at completely different positions - Currently, it'll only search the first level for a key, which can lead to unwanted effects, if you're not using a standard layout or trying to access positions that are not on the first level on the standard layout. I created a bug for this, but it's not been fixed yet. (In reply to David Redondo from comment #50) > As this has been mentioned you can now bind arbitrary key combinations to > extra mouse buttons. I just tested it and it works fine for (bound > printscreen to a side button for testing). So I am closing this as resolved. > If it doesnt work for people (as it seems to not do for Bernd) please file a > new bug I experienced two bugs with this, one of which has been fixed, but the other one is still open. Nevertheless, I can use it, working around the limitations of the current system, and have been doing so for more than half a year now on Wayland exclusively without using imwheel or similar. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 RussianNeuroMancer changed: What|Removed |Added CC|russianneuroman...@ya.ru| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #54 from mira...@mirandastreeter.com --- (In reply to Nate Graham from comment #53) > Most of those actions are exposed globally, and either have a keyboard > shortcut bound to them by default, or you can bind one yourself. And you can > also assign arbitrary shell scripts to global keyboard shortcuts. Then you > can bind a mouse button to the keyboard shortcut used to trigger any of > those actions. So the ability is there. Wouldn't binding a keyboard button to a mouse button, followed by an action to a keyboard button, be considered a workaround? The original bug report seems fairly clear. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Nate Graham changed: What|Removed |Added Version Fixed In||6.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #53 from Nate Graham --- Most of those actions are exposed globally, and either have a keyboard shortcut bound to them by default, or you can bind one yourself. And you can also assign arbitrary shell scripts to global keyboard shortcuts. Then you can bind a mouse button to the keyboard shortcut used to trigger any of those actions. So the ability is there. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #52 from Brad Barnett --- Additionally, do note -- what is the scope here? Are there global, and window specific settings? For example, does "bind button 11 to 'move forward to next workspace', mean that this is taken no matter if the mouse is hovering over the desktop, or a window? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #51 from Brad Barnett --- This bug is about being able to bind any action *at all* to the mouse buttons, in X11/xorg, not binding mouse buttons to a key. The prior to responses to this bug, prior to closing, expressed that there was no resolution at all to this bug. So, were you able to; - change workspaces by binding a mouse button, without any additional software (no imwheel!)? - perform any action you can bind a key to? That is, if I can bind a key combo to "minimize window", can I bind a mouse button to that? - change all other buttons already mosue mapped? eg, change from wheel movements to side buttons, or button 11, or whatever, workspace up/down? I don't believe you've read and understood this bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Brad Barnett changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 David Redondo changed: What|Removed |Added CC||k...@david-redondo.de Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #50 from David Redondo --- As this has been mentioned you can now bind arbitrary key combinations to extra mouse buttons. I just tested it and it works fine for (bound printscreen to a side button for testing). So I am closing this as resolved. If it doesnt work for people (as it seems to not do for Bernd) please file a new bug -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Thomas Capricelli changed: What|Removed |Added CC||kdebugs.20.orzelf@spamgourm ||et.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 RM changed: What|Removed |Added CC||r...@richardmay.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #49 from Bernd Steinhauser --- (In reply to Rob Kam from comment #48) > Twenty years later and this is still unresolved? > > Going to System Settings > Input Devices > Keyboard > Advanced > Swap ESC > and Caps Lock is a piece of cake. > > Then going to System Settings > Input Devices > Mouse there is nothing for > changing e.g. > Wheel Down > Screen down > Wheel Up > Screen up > Button Forward > Control + Left click > Button Back > Shift + Left click Well, when you're on Wayland, there is actually an interface for setting up the additional mouse buttons, but it only works for extra mouse buttons (10+) and not for those that are mapped by default (1-9). And at least with the current versions even that is broken, e.g. you can assign a keypress event to a mouse button, but it won't work. In principle if you would like to reassign buttons 8 (back) and 9 (forward), you could remap your mouse so that these are e.g. button 11 and 12 and then you should be able to reassign them to a keyboard combination you could then use. I haven't checked though whether this works, because as mentioned above it's broken. And it should be possible to directly assign mouse buttons in khotkeys (bug 96431). But in general I agree, it should be possible in the kcm to remap mouse buttons to different functions or even a key combination. I would like to have a list of detected mouse buttons, each with a dropdown list and a couple of predefined mouse actions, e.g. the default mouse actions + selected commands (like those listed for the screen edges), e.g. present windows, peek at desktop, activity manager, close tab … And as the final settings I would like to have "Mouse button 10" (if it's button 10) or "Use as hotkey", so that it can be assigned to any (possibly program-dependent) hotkey function and "Key combination". Of course that also means that there is some duplication in the functionality, but I think it would be nice to present a selection of predefined commands to the user. For me, these possibilities are – together with the problem of restarting kwin – the main showstopper to switch to Wayland. On X11, I'm using imwheel, but that doesn't work on Wayland anymore. There are some options out there to get something like imwheel on Wayland, too, but they basically require working around the compositor and usually are way more complicated to setup, so I really would like to avoid those. Plus, I think in 2023, it should be really possible to properly setup your mouse in KDE without needing to fall back to 3rd party programs. :/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 slm33 changed: What|Removed |Added CC|sl...@ya.ru | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Carbug changed: What|Removed |Added CC||b...@caralluin.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Nate Graham changed: What|Removed |Added Blocks||440076 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=440076 [Bug 440076] Lack of mouse profiles -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Rob Kam changed: What|Removed |Added CC||rob...@gmx.com --- Comment #48 from Rob Kam --- Twenty years later and this is still unresolved? Going to System Settings > Input Devices > Keyboard > Advanced > Swap ESC and Caps Lock is a piece of cake. Then going to System Settings > Input Devices > Mouse there is nothing for changing e.g. Wheel Down > Screen down Wheel Up > Screen up Button Forward > Control + Left click Button Back > Shift + Left click -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Rick Stockton changed: What|Removed |Added Assignee|rickstockton@reno-computerh |plasma-b...@kde.org |elp.com | --- Comment #47 from Rick Stockton --- (removed myself as assignee) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #46 from Rick Stockton --- (In reply to Nate Graham from comment #41) > > Even if there's no explicit Qt support (is this still true?) we could still > implement it ourselves on the KDE side. I should note that Qt support is explicitly "good" for X11, and Wayland seems ready for up to 16 buttons. The reasons why I should no longer be the assignee are (1) the fact that I am unqualified to make the 'visionary' choices: which buttons should default to which actions; and (2) the glue which must hold it together (clicks -> signals and slots for "actions") and (3) making coherent updates for all of the programs which should perhaps make use of higher-numbered buttons. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #45 from Rick Stockton --- (In reply to Nate Graham from comment #41) > Re-opening since this is a reasonable request. Binding shortcuts/actions to > additional mouse buttons seems reasonable. > > Even if there's no explicit Qt support (is this still true?) we could still > implement it ourselves on the KDE side. I'm not much of a programmer. It seems that KGlobalAccel would need some new member function signatures, creating a bit of a mess for backward compatibility. Or, would it be better to create an entire new class for "KGlobalMouseAccel" ? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Nate Graham changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Nate Graham changed: What|Removed |Added CC||myr...@kde.org --- Comment #44 from Nate Graham --- *** Bug 424369 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Nate Graham changed: What|Removed |Added CC||ptsel...@outlook.com --- Comment #43 from Nate Graham --- *** Bug 386670 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #42 from Nate Graham --- *** Bug 272728 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Nate Graham changed: What|Removed |Added Product|kdelibs |systemsettings Status|RESOLVED|REOPENED CC||n...@kde.org Version|4.0 |unspecified Resolution|UPSTREAM|--- Summary|support for additional |Support for configuring |mouse buttons |additional mouse buttons Component|general |kcm_mouse --- Comment #41 from Nate Graham --- Re-opening since this is a reasonable request. Binding shortcuts/actions to additional mouse buttons seems reasonable. Even if there's no explicit Qt support (is this still true?) we could still implement it ourselves on the KDE side. -- You are receiving this mail because: You are watching all bug changes.
