Bug in KAction::initPrivate

Ellis Whitehead ellis at kde.org
Thu Sep 26 13:13:55 BST 2002

On Thursday 26 September 2002 11:52, Martijn Klingens wrote:
> ...
> An obvious workaround would be to not pass the slot to the constructor, but
> connect manually to activated() after the object's creation. But after
> rereading the thread I wonder what exactly wouldn't work for you if the
> '{x}' magic is reverted by Simon to KDE 3.0's behaviour. Could you explain?

The '{x}' magic never caused any problems -- the only objection to it is its 
"magicalness". ;)

More information about the kde-core-devel mailing list