More devices into the Shortcut system...

[Rick Stockton]

It is time for us to "Fish, or Cut Byte" on two alternative ways to 
introduce Mouse-Oriented Shortcuts into Qt5 and KDE-Next:

Todd RME has been suggesting a new design- oriented around DBUS. 
Unfortunately, I don't know how to do that coding. Todd, if your design 
gets a more favorable review from THIS group, within the next few days, 
I'll try to assist you in your work (as best as I can; I'm definitely 
not the brightest person here.)

As an alternative, I'm suggesting the idea of enhancing one or two of 
the existing classes: I'd prefer to enhance the current QShortCutEvent 
and QShortCut scheme, so that they can include Mouse Button events 
within a QKeySequence. (This will including the possibility of _only_ 
one or more Mouse Buttons, with no keyboard event at all.) If that 
proves difficult, I could create new Classes to do this-- but I think I 
can use the 'hasExtendedInfo' trick which one of the smart Qt guys has 
used to handle a variety of Signatures in the  QtMouseEvent() code. I 
can work with *this* stuff on my own.

Please give opinions soon, as we have only 3-5 weeks before the Qt5 API 
goes into soft freeze. After we have Mouse Buttons done, the same design 
could be extended to handle other input devices (joystick, multitouch, 
and so on.)