[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 34362] support for additional mouse buttons
From:       rickst29 <rickstockton () reno-computerhelp ! com>
Date:       2011-11-22 23:07:43
Message-ID: E1RSzRH-0007lg-Jp () bugs ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=34362





--- Comment #39 from rickst29 <rickstockton reno-computerhelp com>  2011-11-22 23:07:42 ---
(In reply to comment #37)
> This is great news, but should this bug be closed?  This bug is not just about
> getting the mouse buttons recognized.  In fact, this was *already* possible
> with programs like imwheel and keyboard button mapping in KDE.
> 
> The real point behind this bug is to make it very, very easy to have users
> assign these buttons in KDE to useful functions.

Michael, KDE Bugzilla is "wide open" for comments, and many of these comments
(including some which *I* made) ignore an important aspect of bug management
procedure:

ONE issue == ONE bug. ALWAYS.



We have several other bugs which touch on "using the mouse", and I'm about to
take ownership of (at least!) one of them. I will probably bisect those bugs
even more, because nearly all of them involve more than one programming job,
and because they're full of comments which ask for unrelated things. Here's an
important one, with nearly as many votes as you saw here:
https://bugs.kde.org/show_bug.cgi?id=48062. Please take a look. You'll see that
the 'description' (the title) asks for one very specific thing, but nearly all
of the comments (and even the attachment) are talking about something
completely different.

48062 is about defining the mouse button to emulate a modifier key -- and ONLY
a modifier key. On your keyboard, the modifiers- Shift, Ctrl, Alt, Meta, Num
Lock.... do nothing by themselves. But nearly all of the comments talk about
Actions-- which are typically invoked by a Modifier AND ANOTHER KEY, or (as the
comments request) a mouse click. 

Using a high-numbered mouse button to perform an action
(https://bugs.kde.org/show_bug.cgi?id=96431) involves much, MUCH simpler
programming. But 48062 could be used to provide instant keyboard layout
switching, modifiers which don't even exist on many keyboards (my USA-105
Keyboard has no pre-defined key for MOD3), and better usability for people with
damaged hands.

Exanding the shortcut system, to accept single or multiple mouse clicks as
Events which invoke user-specified actions, is that 3rd bug, 96431. But this
was pre-requisite for both of them: FIRST, we need to be notified of the button
Events. That job is done (mostly.... I've still got coding to do on other Qt5
platforms, such as Wayland. I'll be crdating additional Qt bugs for tracking
work in those modules). That's why this bug is closed.

Your 'main point of the enhancement', and I strongly agree with you, is
(https://bugs.kde.org/show_bug.cgi?id=96431). You may or may not be interested
in 48062, which is a lot harder for me to accomplish- and that's exactly why I
will start on that one sooner. (As happened with this bug, that solution would
lie entirely within Qt.) 

If I didn't explain this well, feel free to come right back and ask me some
more. OK?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]