summaryrefslogtreecommitdiffstats
path: root/doc/html/tqeventloop.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/tqeventloop.html')
-rw-r--r--doc/html/tqeventloop.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/html/tqeventloop.html b/doc/html/tqeventloop.html
index fa115503f..267855afe 100644
--- a/doc/html/tqeventloop.html
+++ b/doc/html/tqeventloop.html
@@ -69,7 +69,7 @@ The TQEventLoop class manages the event queue.
<p>
<p> It receives events from the window system and other sources. It
-then sends them to <a href="ntqapplication.html">TQApplication</a> for processing and delivery.
+then sends them to <a href="tqapplication.html">TQApplication</a> for processing and delivery.
<p> TQEventLoop allows the application programmer to have more control
over event delivery. Programs that perform long operations can
call either processOneEvent() or <a href="#processEvents">processEvents</a>() with various
@@ -104,8 +104,8 @@ A <tt>typedef</tt> to allow various ProcessEvents values to be OR'ed together.
</h3>
Creates a TQEventLoop object, this object becomes the global event loop object.
There can only be one event loop object. The TQEventLoop is usually constructed
-by calling <a href="ntqapplication.html#eventLoop">TQApplication::eventLoop</a>(). To create your own event loop object create
-it before you instantiate the <a href="ntqapplication.html">TQApplication</a> object.
+by calling <a href="tqapplication.html#eventLoop">TQApplication::eventLoop</a>(). To create your own event loop object create
+it before you instantiate the <a href="tqapplication.html">TQApplication</a> object.
<p> The <em>parent</em> and <em>name</em> arguments are passed on to the <a href="tqobject.html">TQObject</a> constructor.
<h3 class=fn><a name="~TQEventLoop"></a>TQEventLoop::~TQEventLoop ()
@@ -161,7 +161,7 @@ exec() to start a local event loop.
special function whenever there are no pending events, use a
<a href="tqtimer.html">TQTimer</a> with 0 timeout. More advanced idle processing schemes can
be achieved using <a href="#processEvents">processEvents</a>().
-<p> <p>See also <a href="ntqapplication.html#quit">TQApplication::quit</a>(), <a href="#exit">exit</a>(), and <a href="#processEvents">processEvents</a>().
+<p> <p>See also <a href="tqapplication.html#quit">TQApplication::quit</a>(), <a href="#exit">exit</a>(), and <a href="#processEvents">processEvents</a>().
<h3 class=fn>void <a name="exit"></a>TQEventLoop::exit ( int&nbsp;retcode = 0 )<tt> [virtual]</tt>
</h3>
@@ -173,7 +173,7 @@ value indicates an error.
<p> Note that unlike the C library function of the same name, this
function <em>does</em> return to the caller -- it is event processing that
stops.
-<p> <p>See also <a href="ntqapplication.html#quit">TQApplication::quit</a>() and <a href="#exec">exec</a>().
+<p> <p>See also <a href="tqapplication.html#quit">TQApplication::quit</a>() and <a href="#exec">exec</a>().
<h3 class=fn>void <a name="exitLoop"></a>TQEventLoop::exitLoop ()<tt> [virtual]</tt>
</h3>