Rename ntqobject*.h and qobject*.cpp to tqobject*

Signed-off-by: Michele Calgaro <[email protected]>

1 files changed, 9 insertions, 9 deletions

diff --git a/doc/html/timers.html b/doc/html/timers.html
index 65e772d77..7c9415a1c 100644
--- a/doc/html/timers.html
+++ b/doc/html/timers.html
@@ -33,11 +33,11 @@ body { background: #ffffff; color: black; }
 
 
 
-<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
+<p> <a href="tqobject.html">TQObject</a>, the base class of all TQt objects, provides the basic timer
+support in TQt. With <a href="tqobject.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="ntqobject.html#killTimer">TQObject::killTimer</a>() with
+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
@@ -53,7 +53,7 @@ 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
 provides regular timers that emit a signal when the timer fires, and
-inherits <a href="ntqobject.html">TQObject</a> so that it fits well into the ownership structure
+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 );
@@ -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="ntqobject.html">TQObject</a>
+    class Mandelbrot : public <a href="tqobject.html">TQObject</a>
     {
         <a href="metaobjects.html#TQ_OBJECT">TQ_OBJECT</a> // required for signals/slots
     public:
-        Mandelbrot( <a href="ntqobject.html">TQObject</a> *parent=0, const char *name );
+        Mandelbrot( <a href="tqobject.html">TQObject</a> *parent=0, const char *name );
         ...
     public slots:
         void start();
@@ -108,10 +108,10 @@ single-threaded application without blocking the user interface.
     // Constructs and initializes a Mandelbrot object.
     //
 
-    Mandelbrot::Mandelbrot( <a href="ntqobject.html">TQObject</a> *parent=0, const char *name )
-    : <a href="ntqobject.html">TQObject</a>( parent, name )
+    Mandelbrot::Mandelbrot( <a href="tqobject.html">TQObject</a> *parent=0, const char *name )
+    : <a href="tqobject.html">TQObject</a>( parent, name )
     {
-        <a href="ntqobject.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="ntqtimer.html#timeout">timeout</a>()), TQ_SLOT(calculate()) );
         ...
     }