Fwd: Global Shortcuts
ahartmetz at gmail.com
Wed Mar 5 12:36:01 GMT 2008
Am Dienstag 04 März 2008 00:45:42 schrieb Michael Jansen:
> On Monday 03 March 2008 14:25:05 David Faure wrote:
> > On Thursday 28 February 2008, Michael Jansen wrote:
> > > But if we keep the change its current form it is possible for an user
> > > to make each and every action a global action. A programmer has no way
> > > to prevent that.
> > If I want to configure my KDE so that Ctrl+Alt+C executes "new composer
> > window" in kmail, whereever the focus currently is, why should a
> > programmer (i.e. the KAction design) prevent me from doing that? I don't
> > understand why we would want to limit configurability arbitrarily.
> > (Yes there other ways of doing the above example, like khotkeys and
> > running "kmail --composer" there, but that's just one example, and "kmail
> > --composer" requires command-line knowledge, while setting a global
> > shortcut in the shortcut configuration dialog does not)
> > I thought "globalShortcutAllowed" was more of a setEnabled() call;
> > enabling/disabling the shortcut at a given time, with the possibility
> > that a change in the state of the application might toggle this later on.
> Looking at andreas patch i would say's youre understanding was correct. I
> will fix kcm_keys when andreas commits.
Right, my patch also tries not to change existing behavior *too much* so that
applications won't need much porting. The main rationale is that the kdelibs
code is released now so breaking any old compiled application *at all* is a
no-no. That will not be fulfilled in all cases but it will in my opinion (and
there were no protests really) be close enough.
> @andreas please inform me when commiting. I guess next monday?
Mike: Will do, and I guess next monday too.
More information about the kde-core-devel