Update to latest tqt3 automated conversion

1 files changed, 17 insertions, 17 deletions

diff --git a/doc/html/signalsandslots.html b/doc/html/signalsandslots.html
index 4cca6721b..0421e7bcf 100644
--- a/doc/html/signalsandslots.html
+++ b/doc/html/signalsandslots.html
@@ -70,8 +70,8 @@ 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="qobject.html">TQObject</a> or one of its subclasses
-(e.g. <a href="qwidget.html">TQWidget</a>) can contain signals and slots. Signals are emitted by
+<p> All classes that inherit from <a href="ntqobject.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
 does not know or care whether anything is receiving the signals it
@@ -107,7 +107,7 @@ mechanism.
  
 <p> A small TQt class might read:
 <p> <pre>
-    class Foo : public <a href="qobject.html">TQObject</a>
+    class Foo : public <a href="ntqobject.html">TQObject</a>
     {
         <a href="metaobjects.html#Q_OBJECT">Q_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="qobject.html#disconnect">TQObject::disconnect</a>().
+break a connection using <a href="ntqobject.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.
@@ -201,9 +201,9 @@ is emitted.
 and must not be implemented in the <tt>.cpp</tt> file. They can never have
 return types (i.e. use <tt>void</tt>).
 <p> A note about arguments. Our experience shows that signals and slots
-are more reusable if they do <em>not</em> use special types. If <a href="qscrollbar.html#valueChanged">TQScrollBar::valueChanged</a>() were to use a special type such as the
+are more reusable if they do <em>not</em> use special types. If <a href="ntqscrollbar.html#valueChanged">TQScrollBar::valueChanged</a>() were to use a special type such as the
 hypothetical <tt>TQRangeControl::Range</tt>, it could only be connected to
-slots designed specifically for <a href="qrangecontrol.html">TQRangeControl</a>. Something as simple as
+slots designed specifically for <a href="ntqrangecontrol.html">TQRangeControl</a>. Something as simple as
 the program in <a href="tutorial1-05.html">Tutorial #1 part 5</a>
 would be impossible.
 <p> <h2> Slots
@@ -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="qobject.html#className">class name</a>. You can also check if an object
-<a href="qobject.html#inherits">inherits</a> a specific class, for example:
+<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> <pre>
   if ( widget-&gt;inherits("TQButton") ) {
         // yes, it is a push button, radio button etc.
@@ -270,16 +270,16 @@ doesn't TQt use templates for signals and slots?</a>.)
  
 <p> <h2> A Real Example
 </h2>
-<a name="5"></a><p> Here is a simple commented example (code fragments from <a href="qlcdnumber-h.html">qlcdnumber.h</a> ).
+<a name="5"></a><p> Here is a simple commented example (code fragments from <a href="qlcdnumber-h.html">ntqlcdnumber.h</a> ).
 <p> <pre>
-    #include "qframe.h"
-    #include "qbitarray.h"
+    #include "ntqframe.h"
+    #include "ntqbitarray.h"
 
-    class TQLCDNumber : public <a href="qframe.html">TQFrame</a>
+    class TQLCDNumber : public <a href="ntqframe.html">TQFrame</a>
 </pre>
  
-<p> <a href="qlcdnumber.html">TQLCDNumber</a> inherits <a href="qobject.html">TQObject</a>, which has most of the signal/slot
-knowledge, via <a href="qframe.html">TQFrame</a> and <a href="qwidget.html">TQWidget</a>, and #include's the relevant
+<p> <a href="ntqlcdnumber.html">TQLCDNumber</a> inherits <a href="ntqobject.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>
     {
@@ -293,7 +293,7 @@ you have probably forgotten to <a href="moc.html">run the moc</a> or to
 include the moc output in the link command.
 <p> <pre>
     public:
-        <a href="qlcdnumber.html">TQLCDNumber</a>( <a href="qwidget.html">TQWidget</a> *parent=0, const char *name=0 );
+        <a href="ntqlcdnumber.html">TQLCDNumber</a>( <a href="ntqwidget.html">TQWidget</a> *parent=0, const char *name=0 );
         TQLCDNumber( uint numDigits, TQWidget *parent=0, const char *name=0 );
 </pre>
  
@@ -308,7 +308,7 @@ ignores member functions.
         void    overflow();
 </pre>
  
-<p> <a href="qlcdnumber.html">TQLCDNumber</a> emits a signal when it is asked to show an impossible
+<p> <a href="ntqlcdnumber.html">TQLCDNumber</a> emits a signal when it is asked to show an impossible
 value.
 <p> If you don't care about overflow, or you know that overflow cannot
 occur, you can ignore the overflow() signal, i.e. don't connect it to
@@ -334,7 +334,7 @@ indicates, to set the displayed number. Since <tt>display()</tt> is part
 of the class's interface with the rest of the program, the slot is
 public.
 <p> Several of the example programs connect the newValue() signal of a
-<a href="qscrollbar.html">TQScrollBar</a> to the display() slot, so the LCD number continuously shows
+<a href="ntqscrollbar.html">TQScrollBar</a> to the display() slot, so the LCD number continuously shows
 the value of the scroll bar.
 <p> Note that display() is overloaded; TQt will select the appropriate version
 when you connect a signal to the slot. With callbacks, you'd have to find