There's a possibility to set keyboard shortcut for widget, but it mostly dosen't do anything at all.
The only one that I know that works is for Lancelot, all others don't do anything when I press them.
For instance: I have set ctrl+D for show dashboard widget, and I expected that when I'll press this combo the dashboard will be shown but it it isn't.
So what's the deal? Is this not yet finished is it a bug or something completely different.
(I use KDE4.2RC1)

If an applet doesn't have an action defined, I believe it gives the plasmoid keyboard focus, iirc.

Primoz wrote:For instance: I have set ctrl+D for show dashboard widget, and I expected that when I'll press this combo the dashboard will be shown but it it isn't.
(I use KDE4.2RC1)

This particular example really sounds like a missing feature that would be very easy to implement.

GeneralZod wrote:

Primoz wrote:For instance: I have set ctrl+D for show dashboard widget, and I expected that when I'll press this combo the dashboard will be shown but it it isn't.
(I use KDE4.2RC1)

This particular example really sounds like a missing feature that would be very easy to implement.

So what you're saying is that this dosen't exists but it would be easy to implement.
Should I post a wishlist for this on bugs.kde.org??

> Should I post a wishlist for this on bugs.kde.org??

no, because i implemented it last week.

it was a one liner patch for Show Desktop and a 3-4 liner patch for Show Dashboard.

and yes, the idea is that when the keyboard shortcut is triggered it might do something widget-specific (like show the desktop) or it might just give the applet keyboard focus. the latter is an important accessibility feature.

so why have it appear in every widget?

a) because accessibility only works if its pervasive

b) because i want to encourage widget developers to use the activated() signal to Do Cool Stuff(tm), which means shoving it in their face

c) because it allows a universal approach to the shortcut feature


sometimes when you see something in plasma that you don't understand, it is because we have screwed up. more often it's because we just haven't gotten to finishing that part of the experience in the way we want. most often, however, it's because we've thought it through a lot more than the casual user has and realized (more) deep truths than are at first apparent.

there is a reason it took so long to get plasma together. now it moves at an insane pace forward.

those two things are connected.

aseigo wrote:> Should I post a wishlist for this on bugs.kde.org??

no, because i implemented it last week.

it was a one liner patch for Show Desktop and a 3-4 liner patch for Show Dashboard.

and yes, the idea is that when the keyboard shortcut is triggered it might do something widget-specific (like show the desktop) or it might just give the applet keyboard focus. the latter is an important accessibility feature.

so why have it appear in every widget?

a) because accessibility only works if its pervasive

b) because i want to encourage widget developers to use the activated() signal to Do Cool Stuff(tm), which means shoving it in their face

c) because it allows a universal approach to the shortcut feature


sometimes when you see something in plasma that you don't understand, it is because we have screwed up. more often it's because we just haven't gotten to finishing that part of the experience in the way we want. most often, however, it's because we've thought it through a lot more than the casual user has and realized (more) deep truths than are at first apparent.

there is a reason it took so long to get plasma together. now it moves at an insane pace forward.

those two things are connected.

Cool!
Could it be done that in future a keyboard shortcut would bring a certain widget up front (above any opened windows), like it (to some extent) done in Windows 7.
I think that would be the most logical step forward, but maybe that's just me...

Well, this doesn't work for the Search Box. If I have an autohide panel and do Search Box' keyboard shortcut, it pops up the panel but the keyboard focus is not in the Search Box. Should I report this as a bug for the widget?

I would recommend doing so, yes - as this is a Papercut.

bcooksley wrote:I would recommend doing so, yes - as this is a Papercut.

What's a papercut? A very annoying bug?

A Papercut is small issue/bug which is a general annoyance in terms of the usability of an application.