Quote Originally Posted by TheJim01 View Post
I need the ability to communicate with the object running in the thread (sending it signals, or receiving signals from it), but by the documentation, QRunnable doesn't seem to support this type of interaction.
For that you need an event loop. So your previous statement about not needing an event loop could have been premature

If it doesn't derive from QObject, then I can't use signals/slots.
No, you can't declare signals and slots. You can have objects that declare them. But signals won't be delivered to them without an event loop (you can still emit signals though)

I could inherit from both QObject and QRunnable
That wouldn't make much sense. You'd be effectively duplicating QThread.