KGlobalAccel issues

[Lubos Lunak]

 Hello,

 basically, I think I need an update on the plans WRT KGlobalAccel, because I 
finally got tired of not having keyboard shortcuts in KWin working and while 
fixing that I've run into various issues, generally described as "it doesn't 
work":

- It doesn't work. Whoever ported the code consistently used 
KAction::setShortcut() instead of KAction::setGlobalShortcut(). I'll check 
all those set in KControl but if some of your shortcuts not configured there 
don't work check this.

- It doesn't work. What's the point of KAction::setGlobalShortcutAllowed()? If 
a KAction has a global shortcut set, it wants to use it, so why does this 
flag exist at all?

- It doesn't work. Hmm, ok, shortcuts with Alt fixed.

- It finally works, but only if I use all kinds of funny shortcuts, because 
somebody changed all shortcuts to the 4-modifiers scheme by default. What 
exactly is the plan with schemes here? If we default to 4-modifiers I expect 
many people won't be that happy for their shortcuts suddenly changing, people 
with only 3-modifier keyboards probably won't be that happy either. If I pass 
both variants to KAction::setGlobalShortcut() then both will be used if I'm 
getting it right, which is not desired either.

- Some global shortcuts in KWin are of the form "do something with X", where X 
is a number in a range (like, "window to desktop 1" to "20"). KDE3's 
KGlobalAccel allowed connecting a slot with int argument and passed that 
number to it, that doesn't work now. Should I just make separate slots? Not 
that I mind doing that, I just want to know.

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/