Hi,

There's a pretty interesting Ars Technica article about netcode in fighting games. Worth a read.

Hi,

You should rather bring this to the interest mailing list. You'll find there the QtRemoteObject developers/maintainers. This forum is more user oriented.

Just had the same problem, here are my findings:

QRemoteObjectPendingReply inherits from QRemoteObjectPendingCall.

Therefore it inherits the bool waitForFinished(int timeout = 30000) method.

Example:

// DeviceManagerReplica* m_deviceManager // class DeviceManagerReplica created via rep-compiler QRemoteObjectPendingReply<QStringList> result = m_deviceManager->availableDevices(); result.waitForFinished(); qCDebug(lc) << result.returnValue();

waitForFinished() seems to be a sync call, thus the m_deviceManager instance should not live in the main GUI-thread.

Hope this helps.

Hi

I have made it to work.
After rep files are generated with compile error, edit them and paste QDataStream definition before class body. Ifndef is necessary if you have more than one class for remoting with QDomDocument in signal/slot

#ifndef _xml_operator_ #define _xml_operator_ Q_DECLARE_METATYPE(QDomDocument) inline QDataStream& operator<<(QDataStream& out, QDomDocument xml) { out << xml.toString(); return out; } inline QDataStream& operator>>(QDataStream& in, QDomDocument& xml) { QString msg; in >> msg; xml.setContent(msg); return in; } #endif //_xml_operator_

hope it will help somebody

Best Regards
Marek