|Summary:||Add support for Griffin PowerMate|
|Product:||[Applications] systemsettings||Reporter:||Juha Tuomala <tuju>|
|Component:||general||Assignee:||System Settings Bugs <sourtooth+ssbugs>|
|Severity:||wishlist||CC:||nate, rdieter, rjvbertin|
|Latest Commit:||Version Fixed In:|
Description Juha Tuomala 2009-01-13 13:59:07 UTC
Version: (using KDE 4.1.3) Installed from: Fedora RPMs It would be nice to be able to flexibly bind Griffin PowerMate knob to different UI actions in KDE desktop. Typically it's used as volume knob, but if it would be supported enough low level, perhaps it would be useful in other areas too (like zooming in some programs or similar). Also, such configuration should not be limited to one knob instance per system. Kernel support for this device is working. http://en.wikipedia.org/wiki/Griffin_PowerMate
Comment 1 Andreas Pakulat 2009-01-13 15:40:06 UTC
There's nothing KDE has to do with this, you need to talk to X11 developers to make X11 provide the apropriate X11 events for such a tool.
Comment 2 Juha Tuomala 2009-01-13 15:54:13 UTC
And how would that make those configuration dialogs to appear into systemsettings?
Comment 3 Rex Dieter 2009-01-13 15:58:12 UTC
I wonder if this is supported by libsixdof: http://freshmeat.net/projects/libsixdof/ http://akademy.kde.org/conference/presentation/27.php
Comment 4 Andreas Pakulat 2009-01-13 16:16:09 UTC
How this would be configured (if at all) depends on how X11 implements support for such a device. Wether its supported as pointer or keyboard, or something totally different. Only for the latter is a new config dialog needed then.
Comment 5 Juha Tuomala 2009-01-13 16:22:12 UTC
It's a wish, not a bug report. I can imagined that X11 folks say that there is no real demand for it as it's such a niche item and we never can prove it unless we're able to track such need. I don't see any better place for such tracking process than KDE user community.
Comment 6 Andreas Pakulat 2009-01-13 16:58:52 UTC
To support such devices in a general manner for different actions in KDE's GUI it needs to be an input device on the X11 level providing the apropriate input events (pointer movements/clicks or keyboard events). For that to happen you need to file a wish with Xorg. If you just want to support specific stuff in a particular app (or apps) then you should file wishlist reports with those apps. And if this is about a new config GUI for systemsettings for something like gizmod or the libsixdof then you should file it against systemsettings
Comment 7 Juha Tuomala 2009-01-13 18:08:49 UTC
(In reply to comment #6) > To support such devices in a general manner for different actions in KDE's GUI > it needs to be an input device on the X11 level providing the apropriate input > events (pointer movements/clicks or keyboard events). For that to happen you > need to file a wish with Xorg. http://www.the-martins.org/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=3&page=1 > With Evrouter any HID device can be used to generate any X Event you like. So is there still some reason why this could not be an open wish here?
Comment 9 Juha Tuomala 2009-01-13 18:12:30 UTC
http://www.bedroomlan.org/~alexios/coding_evrouter.html > An Input Event Router for Linux
Comment 10 Andreas Pakulat 2009-01-13 18:45:28 UTC
As I said, if you want a KDE config interface for one of those libraries and it should be in systemsettings: File a wish against systemsettings. If you want a config interface for some specific things in an app (or two) file wishes for such configuration in those apps. kdelibs is simply the wrong place for this configuration GUI and as you still don't explain what exactly you want I can't even re-assign this wish anywhere. But indeed it seems the upstream resolving is not right as far as I understood you now. So if you can let me know what of the above you want to have I can re-assign this, else I'll just close as invalid.
Comment 11 Kevin Kofler 2009-01-13 19:12:20 UTC
Reassigning to systemsettings at the reporter's request.
Comment 12 Erik Elsom 2009-11-03 23:59:50 UTC
*** This bug has been confirmed by popular vote. ***
Comment 13 Nate Graham 2020-10-12 23:57:33 UTC
This device was discontinued in 2018. While I'm sure there are a bunch of people out there who still have them, I don't know that we'll be able to prioritize adding support, sorry. :) Of course, if anyone submits a merge request, we'll faithfully evaluate it.