summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/qtimer.3qt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man/man3/qtimer.3qt')
-rw-r--r--doc/man/man3/qtimer.3qt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/man/man3/qtimer.3qt b/doc/man/man3/qtimer.3qt
index 2e80611f7..4aae0dedf 100644
--- a/doc/man/man3/qtimer.3qt
+++ b/doc/man/man3/qtimer.3qt
@@ -84,7 +84,7 @@ This can be used to do heavy work while providing a snappy user interface:
.br
.fi
.PP
-myObject->processOneThing() will be called repeatedly and should return tquickly (typically after processing one data item) so that Qt can deliver events to widgets and stop the timer as soon as it has done all its work. This is the traditional way of implementing heavy work in GUI applications; multi-threading is now becoming available on more and more platforms, and we expect that null events will eventually be replaced by threading.
+myObject->processOneThing() will be called repeatedly and should return quickly (typically after processing one data item) so that Qt can deliver events to widgets and stop the timer as soon as it has done all its work. This is the traditional way of implementing heavy work in GUI applications; multi-threading is now becoming available on more and more platforms, and we expect that null events will eventually be replaced by threading.
.PP
Note that QTimer's accuracy depends on the underlying operating system and hardware. Most platforms support an accuracy of 20ms; some provide more. If Qt is unable to deliver the requested number of timer clicks, it will silently discard some.
.PP