Re: [Development] Why is QSignalSpy using Qt::DirectConnection?

2014-10-26 Thread Thiago Macieira
On Sunday 26 October 2014 16:34:29 Roland Winklmeier wrote: > The easiest fix would be to make QTestEventLoop::exitLoop() thread-safe > by adding the if condition at the beginning of the method: > > if (thread() != QThread::currentThread()) > { > QMetaObject::invokeMethod(this, "exitLoop", Qt:

Re: [Development] Why is QSignalSpy using Qt::DirectConnection?

2014-10-26 Thread Roland Winklmeier
As promissed I had a look into QTestEventLoop. > QSignalSpy::wait() isn't thread-safe because it's using QTestEventLoop > instead > of a regular QEventLoop. That former does use a timer and, unlike the latter, > you can't stop the loop from outside the loop's own thread. Just to be sure: The r

Re: [Development] QtRemoteObjects (was Replicant)

2014-10-26 Thread charleyb123 .
> > Sayeth Simon: > > On the other hand I think it is critical for Qt's success to also support > use- > > cases that leave our little universe (of Qt). And that means either > building > > something yourself and convincing others to adopt it or adopt a > > technology/approach that already has exis