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

List:       kde-bugs-dist
Subject:    [Bug 96431] Ability use mouse buttons for shortcuts
From:       rickst29 <rickstockton () reno-computerhelp ! com>
Date:       2011-08-02 5:42:29
Message-ID: E1Qo7kL-00021g-ED () bugs ! kde ! org
[Download RAW message or body]

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


rickst29 <rickstockton@reno-computerhelp.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rickstockton@reno-computerh
                   |                            |elp.com




--- Comment #30 from rickst29 <rickstockton reno-computerhelp com>  2011-08-02 05:42:26 ---
The description talks about using only "BACKBUTTON and "FORWARDBUTTON", which
CAN be done since Qt 4.7 - If the Programmer chooses to execute code upon the
occurrence of Events from these Buttons.

Qt made a strange choice in naming them as "XButton1" and "XButton2"; These
buttons (Raw Button 8, and Raw Button 9) are widely understood to be "Back" and
"Forward", respectively.
---- 

The purpose of my post this evening, however, is to State that I can "fix"
Qt/x11. With relatively easy code and namespace changes, Qt can emit
MouseButtonPress, MouseButtonRelease, and MouseButtonDoubleClick ** FOR ALL 32
POSSIBLE MOUSE BUTTONS **. And, a "Release" containing this code will remain
backward-compatible with code compiled against earlier Releases of Qt 4.x (No
re-compile would be needed needed.)

I can almost certainly add a new function to provide a full-width Mouse Button
StateMask, as well. And so: If YOU want to define "Global Shortcuts" in KWin,
or you want to program multi-button Mouse codes into a program you're writing,
or you want to create special key+button codes, you can do it by invoking the
'READ' function on the ButtonStateMask when your keystroke event arrives.

You will get the mask AT THAT MOMENT. And so, even if the mouse button has been
held down from "outside", before entering your widget, you can see that it's
down without getting an interrupt. With this knowledge, your program can
execute any branch/control structure you care to write for that combination.

This also holds for multiple concurrent mouse buttons. For example: The
combination of "Button13" double-clicked, with RIGHTBUTTON held down when the
ButtonDblClick Event is issued, can be made to invoke different code than
"Button13" alone. With a gamer-type Mouse, like my own Logitech G700, you could
define *dozens* of unique shortcuts. And they'd all be executable with the
right hand only, with no need to reach for the Keyboard.

If you all can establish the necessity of this "enhancement/fix" with the Qt
people, the code for x11 is easy.

-- 
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]