diff options
| author | Safiyyah Moosa <safiyyah.moosa@qt.io> | 2024-10-21 23:33:52 +0200 |
|---|---|---|
| committer | Safiyyah Moosa <safiyyah.moosa@qt.io> | 2024-11-05 17:32:39 +0100 |
| commit | 371872af23c1c9f9b3b56dd191fb13f850615dd4 (patch) | |
| tree | e66ae896ddf4763e5cdd3f7490e8a7912e4673bd /src/corelib/io/qdebug.cpp | |
| parent | 3ccb4ce781463f1b8e0cb4c9283b3067fe92a32e (diff) | |
Doc: Clarify run() and started() order in QThread
This fix addresses a customer suggestion to clarify the QThread()
documentation. It now states that started() is emitted by the newly
started thread, so any slots connected to it will occur by queued
invocation. For clarity purposes, an additional sentence has been
added to state that whilst the event may have been posted before
run() is called, cross-thread delivery of the signal may still
be pending. A link to 'Signals and Slots Across Threads' has also
been added.
Fixes: QTBUG-112221
Pick-to: 6.5 6.7 6.8
Change-Id: Id502eb4bf48b745af4d9906d7cd05de73d2b6418
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Diffstat (limited to 'src/corelib/io/qdebug.cpp')
0 files changed, 0 insertions, 0 deletions