Databases
StackOverflow2013
Postsdbo
POCombing an External Event Loop with Qt's
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCombing an External Event Loop with Qt's
    text
    copied!<p>I'm building a Qt client for the open-source client/server 4X strategy game <a href="http://www.thousandparsec.net" rel="nofollow noreferrer">Thousand Parsec</a>. This a Google Summer of Code project. I'm however stuck at a dead end. Basically, the client interfaces with the server via a C++ protocol layer that facilitates client/server communication. The protocol's documentation is available <a href="http://www.thousandparsec.net/tp/dev/documents/libtpproto-cpp/html/index.html" rel="nofollow noreferrer">here</a>.</p> <p>Now my problem is that the protocol requires you to create a subclass of the virtual EventLoop class (<a href="http://www.thousandparsec.net/tp/dev/documents/libtpproto-cpp/html/classTPProto_1_1EventLoop.html" rel="nofollow noreferrer">link</a>) in your client. There is an example SimpleEventLoop used for console clients on the same link. I'm having difficulty figuring out how I can design my own event loop subclass that handles the protocol's events while hooking into the Qt application at the same time. My research has lead me to believe <a href="http://doc.qt.io/qt-5/qabstracteventdispatcher.html" rel="nofollow noreferrer">QAbstractEventDispatcher</a> is the Qt class I want to use but the documentation seems pretty slim and I'm not exactly sure how I would go about doing this. </p> <p>Does anyone else have experience linking external event loops with a Qt application? I've also found this <a href="http://doc.trolltech.com/solutions/4/qtmotifextension/qtmotif-overview.html" rel="nofollow noreferrer">example</a> on the Qt page but it wasn't very helpful - or at least I didn't really understand it.</p> <p>Thanks!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload