On Fri, Jun 4, 2010 at 3:51 PM, Alessandro Diaferia <alediafe...@gmail.com> wrote: > How should I handle such events in order to allow further extension via > other kind of input devices? Any hint for me?
I think the ideal solution would be for the KDE shortcut system to be changed to a pluggable system where people can write backend plug-ins to provide support for additional input sources. This would allow the existing shortcut system to directly use buttons from other input devices as shortcuts. So joystick buttons, bluetooth device buttons, mouse buttons, remote control buttons, the wii remote, and so on could be used as shortcuts for anything in KDE as long as long as someone write a backend. They wouldn't have to be buttons, either, voice commands could be used as well. This would mean all of KDE would benefit from any additional input device plugins someone created for his or her own needs, instead of what we have now where if it isn't a keyboard every part of KDE has its own independent implementation (like plasma's handling of mouse button combos) or there needs to be a separate application mapping buttons presses to either keyboard combos or dbus (like kremotecontrol). KDE's lack of integration of non-keyboard input devices (particularly mice) is a long-standing issue, and I think a general solution is better than the piecemeal approach we have now. See here for a longer explanation: https://bugs.kde.org/show_bug.cgi?id=171295 -Todd _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel