[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-21 5:04:31
Message-ID: bug-96431-17878-ixOI7fb2WE () 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|kcmkeys                     |kcmmouse
           Assignee|rickstockton@reno-computerh |nolden@kde.org
                   |elp.com                     |

--- Comment #42 from Rick Stockton <rickstockton@reno-computerhelp.com> ---
Within Qt the Performance cost, and added maintenance headache, is unnaceptable
-- especially since deriving 'QMouseSequence' from 'QKeySequence' would do
nothing for QML. With both Widgits and QML, mouse focus "reaches back" into
parent widgets and QML MouseAreas, ultimately (if no one accepts the event)
reaching KWin anyway.

I am discontinuing work on this, WRT enhancement to Qt5. Whether KDE should
have Desktop shortcuts and GUI, with Human Interface Guidelines for using
exotic mouse button combinations (i.e., press of one button, with drag, while
holding another ... or using high-numbered buttons on non-traditional way) ... 
I will leave to KDE Developers who understand KDE shortcuts better than I do.

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