On Tuesday 14-04-2009 01:25:20 Aaron J. Seigo wrote: > On Monday 13 April 2009, Emdek wrote: >> On Monday 13-04-2009 19:39:00 Aaron J. Seigo wrote: >> > On Sunday 12 April 2009, Emdek wrote: >> >> On Sunday 12-04-2009 18:23:00 Aaron J. Seigo <ase...@kde.org> wrote: >> >> > On Sunday 12 April 2009, Emdek wrote: >> > yes, i don't think it's worth it for the benefit. >> >> Ok, but I'm still thinking that there could be some general information >> on >> shortcut page, that says that triggering that shortcut will gave >> keyboard >> focus to that applet etc. What do you thing about this kind of >> description? > > it would mean: > > * another setter in Applet > * another QString we hang onto for the life of the Applet object > > couldn't we just put a generic "Activate" string there instead? not > precise, > but i'm not sure precision matters here (esp at the costs above)
I was thinking about kind of that kind generic description all the time. ;-) Sorry for being not enough precise. >> > when creating the shortcuts page, go through all actions in d->actions >> > and add >> > them to the page. >> >> So maybe there could be added method that returns list of actions that >> we >> want to add to configuration dialog, similar to that for contextual >> actions? > > we already have an addAction() method. if the action is added there we > can > allow a shortcut for it. Right, I forgot about this... >> Then we could check if it is global or not using >> isGlobalShortcutEnabled() and then display two group boxes, one for >> local >> and one for global shortcuts. > > right ... or we could just use the KShortcutsEditor widget there even, > after > filtering out the 'global' actions (remove, configure, etc) Good idea. But we need to rename that page to "Keyboard shortcuts" then. >> So what solution you suggest for that problem when we want to use >> activated() to tell panel to unhide (like in Tasks applet) and use it's >> activation shortcut to perform action? Should be there added new action >> with global shortcut? > > the panel unhiding and activate() being called are two wholey unrelated > activities. in fact, panel unhiding is completely transparent to > Containment > and must remain that way (it's a View thing, and in this case a View > thing in > plasma-desktop; don't think of "plasma" as "that binary called plasma- > desktop", as plasma-desktop is just one possible incarnation of things, > and > those other things may have no panels or no panels that can hide; this > means > that Containment and View must be kept as separate as possible.) > > so when the global shortcut is triggered, the applet will say "hey, i > think i > need to be seen now" and that will percolate up through the containment > and > then thew view might say "oh, i have to do something special now" > > for DesktopView that might mean calling forward the dashboard or invoking > "show desktop"; the PanelView that might mean unhiding. for another View > it > might mean nothing at all :) Ok, so I'll try to work around this problem in my case. _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
