QThread emits finished() signal but isRunning() returns true and isFinished() returns false

a 夏天 提交于 2019-11-27 20:17:20

The way the QThread lifecycle works is like this:

  1. You call QThread::start().
  2. At this point, isRunning() should start returning true.
  3. The thread internals start. They emit the started() signal.
  4. The thread internals call run().
  5. Unless you override this in a subclass, run() calls exec().
  6. exec() enters an event loop and stays there until quit() or exit() is called.
  7. exec() and run() return to the internals.
  8. At this point, isFinished() should start returning true and isRunning() false.
  9. The internals emit the finished() signal.
  10. The internals do some final cleanups.
  11. The thread terminates for real.

So you need to call quit() after your location fetcher is done - but this->quit() isn't calling quit() on the thread! This is probably why it's not doing anything.

Your code looks a bit like it was patterned after this article:

http://mayaposch.wordpress.com/2011/11/01/how-to-really-truly-use-qthreads-the-full-explanation/

Note how she gives her worker a finished() signal (not the same as QThread::finished) and connects it to the QThread::quit() slot.

It's intended behavior that the thread doesn't quit until you manually terminate it. The thread object hosts an event loop, so it doesn't Finish until the event loop quits, as Sebastian explained.

In short, your signal-slot connections are backwards conceptually - the object should terminate the thread when it is finished doing its thing, not the other way around.

Which Qt version do you use?

Qt 4.8 returned wrong values until 4.8.4 (Qt bug 30251). This bug has been fixed in 4.8.5.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!