Version: (using KDE 4.1.3) OS: Linux Installed from: SuSE RPMs It is very confusing that the example in "Examples" -> "Perform D-Bus Call"-Action does not work at all! (Of course it is disabled, being an example, but I mean that the "TRY"-Button in the "D-Bus Call Settings"-Tab does not do anything, since the settings are simply wrong. Note that the "TRY"-Button works if proper values are entered.) _This_is_problematic_, since D-Bus Actions in "System Settings" -> "Advanced" -> "Shortcuts" have a different naming convention than the values shown by the D-Bus Browser (helpfully offered through a button in the "D-Bus Call Settings"-Tab). So it took me a while to find out that, e.g. Remote Application = org.kde.plasma Remote Object = /App Called Function = local.PlasmaApp.toggleDasboard where the correct values required to show the Dashboard (which I bound to a mouse gesture), since the D-Bus Browser does not have "Application" or "Object" written somewhere. Therefore a working example would be useful (and is easy to achieve anyway). Thanks!
NOTE: It is especially confusing that the D-Bus Viewer writes "App/" while the Remote Object Field requires the entry "/App". How is the user supposed to know that the Slash has to be swapped?
Sorry for the confusion ... We (I am) busy trying to get khotkeys really work. I will fix this.
No trouble! ;) Actually it seems to work just fine otherwise, at least I did not notice anything else not working with it. THANKS! It is very nitpicky with the mouse-gestures though. I have to repeat a gesture several times until it is recognised. However, I have not used mouse gestures before, so I might be just to stupid for that feature. What I also do find confusing is the sorting of the global shortcuts by KDE component (under Keyboard&Mouse). How am I supposed to know which component is responsible? But that may not be related to khotkeys, or is it?