On quinta-feira, 30 de janeiro de 2014 16:51:41, Philipp Kursawe wrote:
> Such operation should be possible, yet it fails cause setProperty calls:
>
> QDynamicPropertyChangeEvent ev(name);
> QCoreApplication::sendEvent(this, &ev);
>
> sendEvent cannot be called from another thread the object does
Hi Phillip,
No, across threads you have to use postEvent. sendEvent delivers the
event directly to the receiver eventHandler, so you would have the
eventHandler running from another thread.
http://qt-project.org/doc/qt-5.0/qtcore/qcoreapplication.html#postEvent
Bo.
Den 30-01-2014 16:51, Phili
Such operation should be possible, yet it fails cause setProperty calls:
QDynamicPropertyChangeEvent ev(name);
QCoreApplication::sendEvent(this, &ev);
sendEvent cannot be called from another thread the object does not belong
to. Is this a bug? Shouldn't that be postEvent instead?
