*** Bug 424369 has been marked as a duplicate of this bug. ***
--
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
*** Bug 272728 has been marked as a duplicate of this bug. ***
--
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
*** Bug 386670 has been marked as a duplicate of this bug. ***
--
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
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 received this bug notification because you are a membe
(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 m
(removed myself as assignee)
--
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 g
(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 shou
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
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
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 received this bug notification
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 thos
(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 t
(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
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 received thi
(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
(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
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
But
(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
** Changed in: kdelibs
Status: Won't Fix => Unknown
--
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
** Changed in: kdelibs
Status: Unknown => Fix Released
--
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
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/62949
Title:
No way to configure mouse button nu
Launchpad has imported 41 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=34362.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launch
** Changed in: kdelibs
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/62949
Title:
No way to configure mouse button number
Status in
23 matches
Mail list logo
