QRemoteObjectReplica.Suspect when busy in while loop
-
I'm working with QRemoteObjectReplica and QRemoteObjectPendingReply::waitForSource function and found out that a while loop (~10sec) in the replica class function causes its state to go from QRemoteObjectReplica::State::Valid to QRemoteObjectReplica::State::Suspect after some seconds and i never receive a replica->isFinished() event on the connected node side.
Is there a way to keep my replica valid/responsive for the other side while its busy with a while loop?
Something like repetitive calls QCoreApplication::processEvents()? -
I'm working with QRemoteObjectReplica and QRemoteObjectPendingReply::waitForSource function and found out that a while loop (~10sec) in the replica class function causes its state to go from QRemoteObjectReplica::State::Valid to QRemoteObjectReplica::State::Suspect after some seconds and i never receive a replica->isFinished() event on the connected node side.
Is there a way to keep my replica valid/responsive for the other side while its busy with a while loop?
Something like repetitive calls QCoreApplication::processEvents()?@majorRonk Why do you need a loop?
-
@majorRonk Why do you need a loop?
@jsulm
The loop has something to do with a special libusb device waiting to be established etc.
I don't want to change the logic of this code (not from me).
Just want to wrap the QRemoteObjectReplica class around it, call it from the connection and wait until its finished
with QRemoteObjectPendingReply
But i guess it works only if the function returns "immediately".
