[Interest] Logging meta call events
Thiago Macieira
thiago.macieira at intel.com
Tue Feb 17 23:54:47 CET 2015
On Tuesday 17 February 2015 23:34:29 Bernhard wrote:
> > If you REALLY need this, you can use the QSignalSpy hook. It won't log
>
> direct
>
> > meta calls like QMetaObject::invokeMethod and events, but it will give you
> > access to all signals and slots as they're called. But you're on your own
>
> if you
>
> > do it. Or instead make a unit test with QtTest and pass the -vs option,
>
> which
>
> > will cause it to log for you.
>
> This would not allow me to integrate the findings into my custom state
> engine log (which also contains transitions and a lot more things in
> chronological order).
The hook itself would. See qsignalspy.cpp for how to install it.
Your callbacks need to be thread-safe.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Interest
mailing list