summaryrefslogtreecommitdiffstats
path: root/doc/src/snippets/code/doc_src_activeqt-dumpcpp.cpp
diff options
context:
space:
mode:
authorKent Hansen <kent.hansen@nokia.com>2011-01-26 11:01:19 (GMT)
committerKent Hansen <kent.hansen@nokia.com>2011-01-26 11:01:19 (GMT)
commit1c79a42d6b0f6c15a0472e0cde3742d0c504ead3 (patch)
tree793c6b796de08f62bd0bbc1b372b12fda5f85b93 /doc/src/snippets/code/doc_src_activeqt-dumpcpp.cpp
parente881b19ba3f2f4bfda460e1a043f461fb0517d70 (diff)
downloadQt-1c79a42d6b0f6c15a0472e0cde3742d0c504ead3.zip
Qt-1c79a42d6b0f6c15a0472e0cde3742d0c504ead3.tar.gz
Qt-1c79a42d6b0f6c15a0472e0cde3742d0c504ead3.tar.bz2
Make sure QStateMachine stops when it's told to
If QStateMachine::stop() was called by an event test or while transitioning to another state, the state machine could end up in an inconsistent internal state (stop==true, but the stopped() signal was not emitted). This also caused the machine to behave incorrectly if it was then restarted (it would immediately stop upon receiving the first event). Solution: Move the stop-handling after the event processing loop, so that it always takes precedence over other possible reasons for exiting the loop (event queues exhausted, final state entered). Task-number: QTBUG-16463 Reviewed-by: Eskil Abrahamsen Blomfeldt
Diffstat (limited to 'doc/src/snippets/code/doc_src_activeqt-dumpcpp.cpp')
0 files changed, 0 insertions, 0 deletions