That's perfectly normal. All connection oriented classes need events to be delivered to work.
Hmm... really? Oh.. you probably use waitForNewConnection(), right? It spawns an internal event loop...I do not need QCoreApplication::exec() or any other related methods.
Some features need QCoreApplication to work, because there is some initialization code there (for instance plugins are loaded from within the application's constructor, so you need to create it regardless if you're going to use it or not). You might safely create your own application instance, just check if some other code hasn't done it earlier (checking QCoreApplication::instance() for null might be enough).The same problem does not occur with TCP sockets. Anyway has any idea how to handle this nicely?
Bookmarks