[PATCH] Configuring global shortcuts

Andreas Hartmetz ahartmetz at gmail.com
Mon Dec 10 16:08:36 GMT 2007

Am Montag 10 Dezember 2007 12:58:47 schrieb Andreas Pakulat:
> On 09.12.07 21:41:15, Aaron J. Seigo wrote:
> > On Sunday 09 December 2007, Andreas Pakulat wrote:
> > > I talked to Andreas Hartmetz a bit on IRC and his opinion is that
> > > there's no need for it, except for a few special cases like kwin,
> > > plasma
> >
> > well, while this is an improvement over the current situation (which is
> > 100% broken, so kudos to you =) there is need for both global defaults
> > (e.g. changing the default for "zoom" for instance) as well as somewhere
> > to set application shortcuts. the latter was something added during the
> > 3.x series based on feedback from users and subsequent testing on a few
> > people that were nearby: when looking to set a keyboard shortcut to
> > launch an app, it was the most common place people went.
IMHO quicklaunch shortcuts belong into the K menu configuration where they 
have been in KDE 3. The backend to actually launch the applications was 
khotkeys IIRC.
Are you saying that users were more likely to find the shortcuts in kcontrol 
than in the K menu configuration? That may be, and in fact I think that both 
are not very good and I don't know a better place either :/

I am also *really* doubtful about the usefulness of changing standard 
shortcuts. I don't see the use case except for people who are used to a 
different scheme, but hey - it's KDE, it's not Windows and it's not Mac OS X 
(*) , so deal with it, users! Sooner or later it does make sense to learn the 
platform's shortcuts anyway. Novices won't be scared much because novices 
don't use keyboard shortcuts.
In fact, I did a bugzilla search and didn't find a single wishlist item asking 
for configurable default shortcuts. Either that was added before anyone asked 
for it or there is no need or my bugzilla search skills are lacking.

(*) For KDE apps running on Windows / Mac OS X it makes perfect sense to use 
*their* schemes, of course.

> I think you're referring to the khotkeys module, which currently sits in
> Systemsettings under Accessiblity. I'm working on that one too, but I
> need some help there, as I can't find out why I get a broken connection
> inside KActionCollection from it (See
> http://lists.kde.org/?l=kde-core-devel&m=119715086719006&w=2 )

More information about the kde-core-devel mailing list