summaryrefslogtreecommitdiffstats
path: root/doc/html/timers.html
diff options
context:
space:
mode:
authorMichele Calgaro <michele.calgaro@yahoo.it>2024-10-15 13:05:33 +0900
committerMichele Calgaro <michele.calgaro@yahoo.it>2024-10-22 10:05:58 +0900
commit397b7afa8e3f32268c4454bf4783ac2a5a799658 (patch)
tree0b41c33e457556bd2b9371788ddbce25263f00d6 /doc/html/timers.html
parent755d46927cc6a5719e695aeb8133be6897de62d8 (diff)
downloadtqt-397b7afa.tar.gz
tqt-397b7afa.zip
Rename ntqapplication, ntqconfig and ntqmodules files to equivalent tq*
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/html/timers.html')
-rw-r--r--doc/html/timers.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/html/timers.html b/doc/html/timers.html
index 4bfcf5848..ce6865026 100644
--- a/doc/html/timers.html
+++ b/doc/html/timers.html
@@ -39,7 +39,7 @@ unique integer timer id. The timer will now "fire" every <em>interval</em>
milliseconds, until you explicitly call <a href="tqobject.html#killTimer">TQObject::killTimer</a>() with
the timer id.
<p> For this mechanism to work, the application must run in an event
-loop. You start an event loop with <a href="ntqapplication.html#exec">TQApplication::exec</a>(). When a
+loop. You start an event loop with <a href="tqapplication.html#exec">TQApplication::exec</a>(). When a
timer fires, the application sends a <a href="tqtimerevent.html">TQTimerEvent</a>, and the flow of
control leaves the event loop until the timer event is processed. This
implies that a timer cannot fire while your application is busy doing