The future of KAction

[Aaron J. Seigo]

On Thursday 10 November 2005 23:38, Hamish Rodda wrote:
> * unplugAll() and isPlugged().  QAction currently does not expose which
> widgets the action is plugged into.  The only way around this that I can
> see would be using a QApplication event filter which watches for add and
> remove action events, and tracks them in KAction.  Deleting the QAction
> automatically removes it from all of the widgets it is plugged into, so the
> same effect could be achieved by deleting the action, and recreating it if
> needed.  Alternatively, the trolls may be persuaded to expose this list if
> we ask very nicely (I think it's reasonable enough).

or they could just add add something like unplugAll() and isPlugged() which 
wouldn't expose any internals. see attached patch against qt-copy for 
example. (haven't tested compilation, etc yet as my qt-copy is currently 
recompiling)

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qt4_qaction.diff
Type: text/x-diff
Size: 1233 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051111/92221acb/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051111/92221acb/attachment.sig>