ambiguity checking seems broken

Michael Jansen kde at
Tue Sep 23 22:24:39 BST 2008

I'm pretty sure that shortcut is ambiguous for you. Works perfectly for me. Do 
you have some additional plugins activated? 

Your error report convinced me to print out one more information in that 
dialog. The actioncollections componentdata name/description.

I will implement that asap. The conflicting actions are reported as ambiguous 
in the round robin procedure(method?). After my change you should be able to 
find out which the offending action are exactly.


On Tuesday 23 September 2008 23:08:17 Andreas Pakulat wrote:
> On 23.09.08 22:23:23, Michael Jansen wrote:
> > On Tuesday 23 September 2008 21:47:39 Andreas Pakulat wrote:
> > > Hi,
> > >
> > > it seems as if the new ambiguity checking for shortcuts has a problem.
> > > I'm getting an ambiguity warning for any action I try to trigger in
> > > konqueror. A first guess would be that this is due to mutliple khtml
> > > xmlgui clients in the same app. Which means shortcuts are in konqueror
> > > totally useless.
> >
> > Some more information would be useful. Which shortcut? The check is only
> > triggered if qt says the shortcut is ambiguous. In that case the the
> > action you intended to trigger wouldn't be triggered anyway because we do
> > not subscribe to ambiguous shortcut events or the
> > QShortcut::activatedAmbiguous() signal.
> Hmm, I thought this was independent of the shortcut, but apparently I
> didn't try enough. In particular Ctrl+F, F3 and Shift+F3 (all of the
> search shortcuts) don't work and this worked until a couple of days ago.
> Andreas

Michael Jansen

More information about the kde-core-devel mailing list