summaryrefslogtreecommitdiffstats
path: root/doc/html/timers.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/timers.html')
-rw-r--r--doc/html/timers.html24
1 files changed, 12 insertions, 12 deletions
diff --git a/doc/html/timers.html b/doc/html/timers.html
index 7c9415a1c..bd53ca7d8 100644
--- a/doc/html/timers.html
+++ b/doc/html/timers.html
@@ -41,7 +41,7 @@ milliseconds, until you explicitly call <a href="tqobject.html#killTimer">TQObje
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
-timer fires, the application sends a <a href="qtimerevent.html">TQTimerEvent</a>, and the flow of
+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
something else. In other words: the accuracy of timers depends on the
@@ -51,26 +51,26 @@ one year is possible). The accuracy depends on the underlying operating
system. Windows 95/98 has 55 millisecond (18.2 times per second)
accuracy; other systems that we have tested (UNIX X11 and Windows NT)
can handle 1 millisecond intervals.
-<p> The main API for the timer functionality is <a href="ntqtimer.html">TQTimer</a>. That class
+<p> The main API for the timer functionality is <a href="tqtimer.html">TQTimer</a>. That class
provides regular timers that emit a signal when the timer fires, and
inherits <a href="tqobject.html">TQObject</a> so that it fits well into the ownership structure
of most GUI programs. The normal way of using it is like this:
<pre>
- <a href="ntqtimer.html">TQTimer</a> * counter = new <a href="ntqtimer.html">TQTimer</a>( this );
- connect( counter, TQ_SIGNAL(<a href="ntqtimer.html#timeout">timeout</a>()),
+ <a href="tqtimer.html">TQTimer</a> * counter = new <a href="tqtimer.html">TQTimer</a>( this );
+ connect( counter, TQ_SIGNAL(<a href="tqtimer.html#timeout">timeout</a>()),
this, TQ_SLOT(updateCaption()) );
- counter-&gt;<a href="ntqtimer.html#start">start</a>( 1000 );
+ counter-&gt;<a href="tqtimer.html#start">start</a>( 1000 );
</pre>
<p> The counter timer is made into a child of this widget, so that when
this widget is deleted, the timer is deleted too. Next, its timeout
signal is connected to the slot that will do the work, and finally
it's started.
-<p> <a href="ntqtimer.html">TQTimer</a> also provides a simple one-shot timer API. <a href="ntqbutton.html">TQButton</a> uses this
+<p> <a href="tqtimer.html">TQTimer</a> also provides a simple one-shot timer API. <a href="ntqbutton.html">TQButton</a> uses this
to show the button being pressed down and then (0.1 seconds later) be
released when the keyboard is used to "press" a button, for example:
<p> <pre>
- TQTimer::<a href="ntqtimer.html#singleShot">singleShot</a>( 100, this, TQ_SLOT(animateTimeout()) );
+ TQTimer::<a href="tqtimer.html#singleShot">singleShot</a>( 100, this, TQ_SLOT(animateTimeout()) );
</pre>
<p> 0.1 seconds after this line of code is executed, the same button's
@@ -100,7 +100,7 @@ single-threaded application without blocking the user interface.
private slots:
void calculate();
private:
- <a href="ntqtimer.html">TQTimer</a> timer;
+ <a href="tqtimer.html">TQTimer</a> timer;
...
};
@@ -111,7 +111,7 @@ single-threaded application without blocking the user interface.
Mandelbrot::Mandelbrot( <a href="tqobject.html">TQObject</a> *parent=0, const char *name )
: <a href="tqobject.html">TQObject</a>( parent, name )
{
- <a href="tqobject.html#connect">connect</a>( &amp;timer, TQ_SIGNAL(<a href="ntqtimer.html#timeout">timeout</a>()), TQ_SLOT(calculate()) );
+ <a href="tqobject.html#connect">connect</a>( &amp;timer, TQ_SIGNAL(<a href="tqtimer.html#timeout">timeout</a>()), TQ_SLOT(calculate()) );
...
}
@@ -122,8 +122,8 @@ single-threaded application without blocking the user interface.
void Mandelbrot::start()
{
- if ( !timer.<a href="ntqtimer.html#isActive">isActive</a>() ) // not already running
- timer.<a href="ntqtimer.html#start">start</a>( 10 ); // timeout every 10 ms
+ if ( !timer.<a href="tqtimer.html#isActive">isActive</a>() ) // not already running
+ timer.<a href="tqtimer.html#start">start</a>( 10 ); // timeout every 10 ms
}
//
@@ -135,7 +135,7 @@ single-threaded application without blocking the user interface.
{
... // perform the calculation for a scanline
if ( finished ) { // no more scanlines
- timer.<a href="ntqtimer.html#stop">stop</a>();
+ timer.<a href="tqtimer.html#stop">stop</a>();
emit done();
}
}