AuroraMiddleware/qt5base-lts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Doc: remove the claim that zero timers execute after GUI events

Browse Source 
This ties our hands on what we can do in our implementations. I don't
care if you've depended on this in your code. It was wrong.

Fixes: QTBUG-80600
Change-Id: I568dea4813b448fe9ba6fffd15de8865a27f0a35
Reviewed-by: Olivier Goffart (Woboq GmbH) <ogoffart@woboq.com>
This commit is contained in:
Thiago Macieira 2019-12-08 15:14:49 -08:00
parent 6bef90f3cf
commit a77fdc9847
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/corelib/kernel/qtimer.cpp
View File

@ -84,10 +84,10 @@ QT_BEGIN_NAMESPACE
must start and stop the timer in its thread; it is not possible to
start a timer from another thread.
As a special case, a QTimer with a timeout of 0 will time out as
soon as all the events in the window system's event queue have
been processed. This can be used to do heavy work while providing
a snappy user interface:
As a special case, a QTimer with a timeout of 0 will time out as soon as
possible, though the ordering between zero timers and other sources of
events is unspecified. Zero timers can be used to do some work while still
providing a snappy user interface:
\snippet timers/timers.cpp 4
\snippet timers/timers.cpp 5