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

List:       kde-core-devel
Subject:    Re: KAction port: do we need to support multiple shortcuts per action?
From:       Hamish Rodda <rodda () kde ! org>
Date:       2005-11-29 16:02:49
Message-ID: 200511300302.52636.rodda () kde ! org
[Download RAW message or body]


On Wednesday 30 November 2005 02:52, Thomas Zander wrote:
> On Tuesday 29 November 2005 16:05, Hamish Rodda wrote:
> > Hi,
> >
> > My port of KAction to use QAction is progressing well (it even looks
> > like QAction could completely replace KAction).  However, it seems that
> > having multiple shortcuts per action will not sustainable in the new
> > model (from discussions held with Simon Hausmann).
> >
> > Trolltech considered supporting multiple shortcuts when they were
> > writing Qt4, but decided against it, due to the complexity it would
> > cause and because it was thought to be bad usability wise.
> >
> > In KDE, multiple shortcuts are the default for cut/copy/paste, as well
> > as occasionally in other places (but are certainly not the norm).
>
> Could you explain more clearly what 'multiple shortcuts' is?
>
> I can imagine 2 things;
> * Having more then one complete shortcut per action.

This is what I meant.  In KDE, this is provided by KShortcut, which can have 
up to 4 separate key sequences (although it seems only 2 are supported by the 
config gui).  In KDE3, KAction allows any of the sequences to activate the 
same action.  If we were to use QAction as a base for KAction in KDE4, to 
keep this feature we (or Trolltech) would have to add multiple sequence 
support.

> * Having to press multiple keysequences per shortcut. (emacs style)

Key sequences are supported (by QKeySequence).

Cheers,
Hamish.

[Attachment #3 (application/pgp-signature)]

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