Quote Originally Posted by Dumbledore View Post
I don't know what you are talking about. My understanding is QThread::run is its own thread, and whatever I do within that thread is part of that thread... (Creating MSocket on the stack would mean that it runs within that thread.)

Is there half decent documentation out there on this? I can't make sense of the QT4 documentation on threads and the book GUI programming with QT doesn't do justice to threading.
Yes, but since the QThread object itself lives in another thread than the MSocket instance, signal slot connections between them get queued by default and therefore corresponding slots might end up being called in different thread than you expect. It all depends what your slots actually do. Check out Brad Hughes' multithreading presentation from Trolltech DevDays 2007: http://chaos.troll.no/~ahanssen/devd...-Threading.pdf, starting from page 33. Also, I noticed usage of both SIGNAL(quit()) and SLOT(quit()), is this intentional?

One negative I have noticed about QT is there's a lack of code examples.
Really? http://doc.trolltech.com/latest/examples.html