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

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

1 files changed, 6 insertions, 6 deletions

diff --git a/doc/html/signalsandslots.html b/doc/html/signalsandslots.html
index e8efd185d..8f453eae4 100644
--- a/doc/html/signalsandslots.html
+++ b/doc/html/signalsandslots.html
@@ -70,7 +70,7 @@ ensures that if you connect a signal to a slot, the slot will be
 called with the signal's parameters at the right time. Signals and
 slots can take any number of arguments of any type. They are
 completely typesafe: no more callback core dumps!
-<p> All classes that inherit from <a href="ntqobject.html">TQObject</a> or one of its subclasses
+<p> All classes that inherit from <a href="tqobject.html">TQObject</a> or one of its subclasses
 (e.g. <a href="ntqwidget.html">TQWidget</a>) can contain signals and slots. Signals are emitted by
 objects when they change their state in a way that may be interesting
 to the outside world. This is all the object does to communicate. It
@@ -107,7 +107,7 @@ mechanism.
  
 <p> A small TQt class might read:
 <p> <pre>
-    class Foo : public <a href="ntqobject.html">TQObject</a>
+    class Foo : public <a href="tqobject.html">TQObject</a>
     {
         <a href="metaobjects.html#TQ_OBJECT">TQ_OBJECT</a>
     public:
@@ -165,7 +165,7 @@ in the case of cyclic connections (e.g. if <tt>b.valueChanged()</tt>
 were connected to <tt>a.setValue()</tt>).
 <p> A signal is emitted for <em>every</em> connection you make, so if you
 duplicate a connection, two signals will be emitted. You can always
-break a connection using <a href="ntqobject.html#disconnect">TQObject::disconnect</a>().
+break a connection using <a href="tqobject.html#disconnect">TQObject::disconnect</a>().
 <p> This example illustrates that objects can work together without knowing
 about each other, as long as there is someone around to set up a
 connection between them initially.
@@ -260,8 +260,8 @@ meta object. The meta object contains the names of all the signal and
 slot members, as well as pointers to these functions. (For more
 information on TQt's Meta Object System, see <a href="templates.html">Why
 doesn't TQt use templates for signals and slots?</a>.)
-<p> The meta object contains additional information such as the object's <a href="ntqobject.html#className">class name</a>. You can also check if an object
-<a href="ntqobject.html#inherits">inherits</a> a specific class, for example:
+<p> The meta object contains additional information such as the object's <a href="tqobject.html#className">class name</a>. You can also check if an object
+<a href="tqobject.html#inherits">inherits</a> a specific class, for example:
 <p> <pre>
   if ( widget-&gt;inherits("TQButton") ) {
         // yes, it is a push button, radio button etc.
@@ -278,7 +278,7 @@ doesn't TQt use templates for signals and slots?</a>.)
     class TQLCDNumber : public <a href="ntqframe.html">TQFrame</a>
 </pre>
  
-<p> <a href="ntqlcdnumber.html">TQLCDNumber</a> inherits <a href="ntqobject.html">TQObject</a>, which has most of the signal/slot
+<p> <a href="ntqlcdnumber.html">TQLCDNumber</a> inherits <a href="tqobject.html">TQObject</a>, which has most of the signal/slot
 knowledge, via <a href="ntqframe.html">TQFrame</a> and <a href="ntqwidget.html">TQWidget</a>, and #include's the relevant
 declarations.
 <p> <pre>