RFC: API and code changes to KShortcut and KAction

Boudewijn Rempt boud at valdyas.org
Fri Nov 24 19:32:41 GMT 2006

On Fri, 24 Nov 2006, Andreas Hartmetz wrote:

> 2006/11/24, Boudewijn Rempt <boud at valdyas.org>:
> > In all of KDE's svn?
> not really, but (in trunk)
> kdelibs
> kdepimlibs
> kdebase
> kdeaccessibility
> kdeadmin
> kdeedu
> kdegraphics
> kdemultimedia
> kdenetwork
> kdepim
> kdesdk
> kdetoys
> kdeutils
> kdevelop
> kdewebdev

So no KOffice?

> > Well, what I really need is per-application shortcut schemes, so I can
> > define
> > a Photoshop compatible shortcut scheme, a Macromedia-compatible
> > shortcut-scheme and perhaps an MS Paint compatible shortcut scheme.
> I don't see the point of such a capability; as people said in the
> window title discussion, the main goal of KDE applications should be
> consistency with other KDE applications. If everybody thought it was a
> good idea - no problem, KStdAccel could just take an "application" or
> "scheme" parameter...

You evidently don't have to deal with Photoshop users giving Krita a try. Or WordPerfect
users trying to use KWord. It's not about the common stuff like cut copy and paste:
it's the specific shortcuts that application experts spend years to get into their fingers.
That's why I really need that feature. In fact, I've got people lined up all ready to
start defining shortcut schemes for Krita as soon as this feature is implemented.


More information about the kde-core-devel mailing list