KAction/KActionCollection proposed changes

[Kevin Ottens]

Le dimanche 28 octobre 2007, Andreas Hartmetz a écrit :
> There is an alternative: catch QEvent::ActionChanged events (probably in an
> event filter on the Q/KApplication) and if it's a KAction do whatever needs
> to be done to make a KAction behave like one. Simon indicated that this
> should work some time ago.
> It's ugly as hell so I didn't even mention it before because I'd like to
> avoid it. But hey, if we need it...

Well yeah, I agree that's ugly as hell. :-)

But really I don't see it required for now, if the KActionCollection API stays 
based on QAction* (except for factory methods) we should be safe. There's not 
that many QAction* provided by Qt widgets right now, and we don't need to put 
fancy stuff on them. What we have now is enough, we should go for the 
ActionChanged event hack only if the current situation is blocking us (but I 
somehow doubt it for now).

Regards.
-- 
Kévin 'ervin' Ottens, http://ervin.ipsquad.net
"Ni le maître sans disciple, Ni le disciple sans maître,
Ne font reculer l'ignorance."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071028/9869a75b/attachment.sig>