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

List:       kde-bugs-dist
Subject:    [Bug 96431] Ability to use mouse buttons for shortcuts
From:       Rick Stockton <rickstockton () reno-computerhelp ! com>
Date:       2012-12-27 6:42:18
Message-ID: bug-96431-17878-4MSvW1Ac6K () http ! bugs ! kde ! org/
[Download RAW message or body]

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

Rick Stockton <rickstockton@reno-computerhelp.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|kcmmouse                    |general
           Assignee|nolden@kde.org              |molkentin@kde.org

--- Comment #43 from Rick Stockton <rickstockton@reno-computerhelp.com> ---
Providing more detail:

The 'scope of work' to make _genuine_ mouse shortcuts within Qt (translating
mouse events into shortcut events, using new Classes derived from QKeySequence
and QShortcutMap) seems very large... and not completely necessary for KDE
purposes. If I understand correctly, the Scheme of QKeySequence <->
QMouseShortcutMap <-> QShortcutEvent, invoking QActions, is required ONLY
because Keyboard does not have "automatic" focus management. But with the
Mouse, MouseArea elements and QWidgets which are "visible" have focus
automatically, and events which were not
accepted get "pushed back" onto their parents/background elements
automatically.

If so, then I think that we do not need to have "mouse shortcut" class within
Qt. Instead, can we just create "Human Interface Guideleines" (HIG) for mouse
within KDE, and advise programmers NOT to use those "shorcuts" incorrectly? And
for the case of "Global shortcuts", can we possibly provide skeleton code, or
an entire Object, which serves as an eventFilter() for pointer events at the
KApplication level?

Although I solved bug 43692, I am not a C++ programmer, and would need guidance
in working on this myself. I would also be VERY slow to create code. So, I
would prefer to contribute by working on the HIG.

In Qt5 , we have a largeer number of "mouse buttons" on most platforms. (16 on
OS-X; 16 or 31 Linux according to your choice of Driver; and 10-16 on
tablet devices). But we will also have a full-width button State mask:
The event /mousebuttons/ mask values are supposed to indicate "Pressed
State" for ALL of the buttons which you have pressed, even when graphics
platform (Wayland, XCB, Cocoa, QNX) provides only a small mask to us.

(In Qt 4.8 and earlier, you can only see "held" State for LeftButton,
RightButton, and MiddleButton).

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]