It's an asynchronous call. The machine will start next time Qt enters the event loop.
It's an asynchronous call. The machine will start next time Qt enters the event loop.
jimiq (19th November 2009)
I have no other events running at that time.
I checked if it was running later in the app and it still comes back with stopped
As already said, provide a minimal compilable example reproducing the problem. I can't help you without knowing what you did.
I managed to find the problem. When you mentioned about it being an asynchronous call got me thinking. I found that I was calling the state machine in the constructor of my dialog and was trying to trigger it too early. I then added a slot/signal combination to wait for the started() signal from the state machine before trying to create the TCP socket and now all appears fine.
Thanks for your help.
Jim
Bookmarks