[Desktop-packages] [Bug 62949]
(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 received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/62949 Title: No way to configure mouse button number Status in kdelibs: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 62949]
(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 received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/62949 Title: No way to configure mouse button number Status in kdelibs: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 62949]
(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 received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/62949 Title: No way to configure mouse button number Status in kdelibs: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp