From c740211ffba3330d951f4c3ddefea8edf23a01cd Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Tue, 7 May 2013 21:58:34 -0500 Subject: Automated update from Qt3 --- doc/man/man3/qtimer.3qt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/man/man3/qtimer.3qt') 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 -- cgit v1.2.3