[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Fwd: Global Shortcuts
From:       David Faure <faure () kde ! org>
Date:       2008-03-03 13:25:05
Message-ID: 200803031425.06335.faure () kde ! org
[Download RAW message or body]

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.

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
[prev in list] [next in list] [prev in thread] [next in thread]