summaryrefslogtreecommitdiffstats
path: root/doc/html/timers.html
diff options
context:
space:
mode:
authorTimothy Pearson <[email protected]>2012-01-26 23:32:43 -0600
committerTimothy Pearson <[email protected]>2012-01-26 23:32:43 -0600
commitea318d1431c89e647598c510c4245c6571aa5f46 (patch)
tree996d29b80c30d453dda86d1a23162d441628f169 /doc/html/timers.html
parentaaf89d4b48f69c9293feb187db26362e550b5561 (diff)
downloadtqt3-ea318d1431c89e647598c510c4245c6571aa5f46.tar.gz
tqt3-ea318d1431c89e647598c510c4245c6571aa5f46.zip
Update to latest tqt3 automated conversion
Diffstat (limited to 'doc/html/timers.html')
-rw-r--r--doc/html/timers.html40
1 files changed, 20 insertions, 20 deletions
diff --git a/doc/html/timers.html b/doc/html/timers.html
index ccf18b0fc..0dc2cd561 100644
--- a/doc/html/timers.html
+++ b/doc/html/timers.html
@@ -33,14 +33,14 @@ body { background: #ffffff; color: black; }
-<p> <a href="qobject.html">TQObject</a>, the base class of all TQt objects, provides the basic timer
-support in TQt. With <a href="qobject.html#startTimer">TQObject::startTimer</a>(), you start a timer with
+<p> <a href="ntqobject.html">TQObject</a>, the base class of all TQt objects, provides the basic timer
+support in TQt. With <a href="ntqobject.html#startTimer">TQObject::startTimer</a>(), you start a timer with
an <em>interval</em> in milliseconds as argument. The function returns a
unique integer timer id. The timer will now "fire" every <em>interval</em>
-milliseconds, until you explicitly call <a href="qobject.html#killTimer">TQObject::killTimer</a>() with
+milliseconds, until you explicitly call <a href="ntqobject.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="qapplication.html#exec">TQApplication::exec</a>(). When a
+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
control leaves the event loop until the timer event is processed. This
implies that a timer cannot fire while your application is busy doing
@@ -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="qtimer.html">TQTimer</a>. That class
+<p> The main API for the timer functionality is <a href="ntqtimer.html">TQTimer</a>. That class
provides regular timers that emit a signal when the timer fires, and
-inherits <a href="qobject.html">TQObject</a> so that it fits well into the ownership structure
+inherits <a href="ntqobject.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="qtimer.html">TQTimer</a> * counter = new <a href="qtimer.html">TQTimer</a>( this );
- connect( counter, SIGNAL(<a href="qtimer.html#timeout">timeout</a>()),
+ <a href="ntqtimer.html">TQTimer</a> * counter = new <a href="ntqtimer.html">TQTimer</a>( this );
+ connect( counter, SIGNAL(<a href="ntqtimer.html#timeout">timeout</a>()),
this, SLOT(updateCaption()) );
- counter-&gt;<a href="qtimer.html#start">start</a>( 1000 );
+ counter-&gt;<a href="ntqtimer.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="qtimer.html">TQTimer</a> also provides a simple one-shot timer API. <a href="qbutton.html">TQButton</a> uses this
+<p> <a href="ntqtimer.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="qtimer.html#singleShot">singleShot</a>( 100, this, SLOT(animateTimeout()) );
+ TQTimer::<a href="ntqtimer.html#singleShot">singleShot</a>( 100, this, SLOT(animateTimeout()) );
</pre>
<p> 0.1 seconds after this line of code is executed, the same button's
@@ -87,11 +87,11 @@ single-threaded application without blocking the user interface.
// has finished. Note that this example is not complete, just an
// outline.
- class Mandelbrot : public <a href="qobject.html">TQObject</a>
+ class Mandelbrot : public <a href="ntqobject.html">TQObject</a>
{
<a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a> // required for signals/slots
public:
- Mandelbrot( <a href="qobject.html">TQObject</a> *parent=0, const char *name );
+ Mandelbrot( <a href="ntqobject.html">TQObject</a> *parent=0, const char *name );
...
public slots:
void start();
@@ -100,7 +100,7 @@ single-threaded application without blocking the user interface.
private slots:
void calculate();
private:
- <a href="qtimer.html">TQTimer</a> timer;
+ <a href="ntqtimer.html">TQTimer</a> timer;
...
};
@@ -108,10 +108,10 @@ single-threaded application without blocking the user interface.
// Constructs and initializes a Mandelbrot object.
//
- Mandelbrot::Mandelbrot( <a href="qobject.html">TQObject</a> *parent=0, const char *name )
- : <a href="qobject.html">TQObject</a>( parent, name )
+ Mandelbrot::Mandelbrot( <a href="ntqobject.html">TQObject</a> *parent=0, const char *name )
+ : <a href="ntqobject.html">TQObject</a>( parent, name )
{
- <a href="qobject.html#connect">connect</a>( &amp;timer, SIGNAL(<a href="qtimer.html#timeout">timeout</a>()), SLOT(calculate()) );
+ <a href="ntqobject.html#connect">connect</a>( &amp;timer, SIGNAL(<a href="ntqtimer.html#timeout">timeout</a>()), SLOT(calculate()) );
...
}
@@ -122,8 +122,8 @@ single-threaded application without blocking the user interface.
void Mandelbrot::start()
{
- if ( !timer.<a href="qtimer.html#isActive">isActive</a>() ) // not already running
- timer.<a href="qtimer.html#start">start</a>( 10 ); // timeout every 10 ms
+ 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
}
//
@@ -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="qtimer.html#stop">stop</a>();
+ timer.<a href="ntqtimer.html#stop">stop</a>();
emit done();
}
}