Update to latest tqt3 automated conversion

1 files changed, 16 insertions, 16 deletions

diff --git a/doc/html/qcopchannel.html b/doc/html/qcopchannel.html
index 4de884fb5..23461cef3 100644
--- a/doc/html/qcopchannel.html
+++ b/doc/html/qcopchannel.html
@@ -35,7 +35,7 @@ body { background: #ffffff; color: black; }
 between several clients.
 <a href="#details">More...</a>
 <p><tt>#include &lt;<a href="qcopchannel_qws-h.html">qcopchannel_qws.h</a>&gt;</tt>
-<p>Inherits <a href="qobject.html">TQObject</a>.
+<p>Inherits <a href="ntqobject.html">TQObject</a>.
 <p><a href="qcopchannel-members.html">List of all member functions.</a>
 <h2>Public Members</h2>
 <ul>
@@ -70,14 +70,14 @@ functions usable without an object.
 <p> The <a href="#channel">channel</a>() function returns the name of the channel.
 <p> In order to <em>listen</em> to the traffic on a channel, you should
 either subclass TQCopChannel and reimplement <a href="#receive">receive</a>(), or
-<a href="qobject.html#connect">connect</a>() to the <a href="#received">received</a>() signal.
+<a href="ntqobject.html#connect">connect</a>() to the <a href="#received">received</a>() signal.
 
 <hr><h2>Member Function Documentation</h2>
-<h3 class=fn><a name="TQCopChannel"></a>TQCopChannel::TQCopChannel ( const&nbsp;<a href="qcstring.html">TQCString</a>&nbsp;&amp;&nbsp;channel, <a href="qobject.html">TQObject</a>&nbsp;*&nbsp;parent = 0, const&nbsp;char&nbsp;*&nbsp;name = 0 )
+<h3 class=fn><a name="TQCopChannel"></a>TQCopChannel::TQCopChannel ( const&nbsp;<a href="ntqcstring.html">TQCString</a>&nbsp;&amp;&nbsp;channel, <a href="ntqobject.html">TQObject</a>&nbsp;*&nbsp;parent = 0, const&nbsp;char&nbsp;*&nbsp;name = 0 )
 </h3>
 Constructs a TQCop channel and registers it with the server using
 the name <em>channel</em>. The standard <em>parent</em> and <em>name</em> arguments
-are passed on to the <a href="qobject.html">TQObject</a> constructor.
+are passed on to the <a href="ntqobject.html">TQObject</a> constructor.
 
 <h3 class=fn><a name="~TQCopChannel"></a>TQCopChannel::~TQCopChannel ()<tt> [virtual]</tt>
 </h3>
@@ -85,16 +85,16 @@ Destroys the client's end of the channel and notifies the server
 that the client has closed its connection. The server will keep
 the channel open until the last registered client detaches.
 
-<h3 class=fn><a href="qcstring.html">TQCString</a> <a name="channel"></a>TQCopChannel::channel () const
+<h3 class=fn><a href="ntqcstring.html">TQCString</a> <a name="channel"></a>TQCopChannel::channel () const
 </h3>
 Returns the name of the channel.
 
-<h3 class=fn>bool <a name="isRegistered"></a>TQCopChannel::isRegistered ( const&nbsp;<a href="qcstring.html">TQCString</a>&nbsp;&amp;&nbsp;channel )<tt> [static]</tt>
+<h3 class=fn>bool <a name="isRegistered"></a>TQCopChannel::isRegistered ( const&nbsp;<a href="ntqcstring.html">TQCString</a>&nbsp;&amp;&nbsp;channel )<tt> [static]</tt>
 </h3>
 Queries the server for the existence of <em>channel</em>.
 <p> Returns TRUE if <em>channel</em> is registered; otherwise returns FALSE.
 
-<h3 class=fn>void <a name="receive"></a>TQCopChannel::receive ( const&nbsp;<a href="qcstring.html">TQCString</a>&nbsp;&amp;&nbsp;msg, const&nbsp;<a href="qbytearray.html">TQByteArray</a>&nbsp;&amp;&nbsp;data )<tt> [virtual]</tt>
+<h3 class=fn>void <a name="receive"></a>TQCopChannel::receive ( const&nbsp;<a href="ntqcstring.html">TQCString</a>&nbsp;&amp;&nbsp;msg, const&nbsp;<a href="qbytearray.html">TQByteArray</a>&nbsp;&amp;&nbsp;data )<tt> [virtual]</tt>
 </h3>
 This virtual function allows subclasses of TQCopChannel to process
 data received from their channel.
@@ -103,15 +103,15 @@ data received from their channel.
 extract the information it contains.
 <p> Example:
 <pre>
-    void MyClass::receive( const <a href="qcstring.html">TQCString</a> &amp;msg, const <a href="qbytearray.html">TQByteArray</a> &amp;data )
+    void MyClass::receive( const <a href="ntqcstring.html">TQCString</a> &amp;msg, const <a href="qbytearray.html">TQByteArray</a> &amp;data )
     {
-        <a href="qdatastream.html">TQDataStream</a> stream( data, <a href="qfile.html#open">IO_ReadOnly</a> );
+        <a href="ntqdatastream.html">TQDataStream</a> stream( data, <a href="ntqfile.html#open">IO_ReadOnly</a> );
         if ( msg == "execute(TQString,TQString)" ) {
-            <a href="qstring.html">TQString</a> cmd, arg;
+            <a href="ntqstring.html">TQString</a> cmd, arg;
             stream &gt;&gt; cmd &gt;&gt; arg;
             ...
         } else if ( msg == "delete(TQString)" ) {
-            <a href="qstring.html">TQString</a> filenname;
+            <a href="ntqstring.html">TQString</a> filenname;
             stream &gt;&gt; filename;
             ...
         } else ...
@@ -126,23 +126,23 @@ requirement. Whatever convention you use the sender and receiver
 <em>must</em> agree on the argument types.
 <p> <p>See also <a href="#send">send</a>().
 
-<h3 class=fn>void <a name="received"></a>TQCopChannel::received ( const&nbsp;<a href="qcstring.html">TQCString</a>&nbsp;&amp;&nbsp;msg, const&nbsp;<a href="qbytearray.html">TQByteArray</a>&nbsp;&amp;&nbsp;data )<tt> [signal]</tt>
+<h3 class=fn>void <a name="received"></a>TQCopChannel::received ( const&nbsp;<a href="ntqcstring.html">TQCString</a>&nbsp;&amp;&nbsp;msg, const&nbsp;<a href="qbytearray.html">TQByteArray</a>&nbsp;&amp;&nbsp;data )<tt> [signal]</tt>
 </h3>
 
 <p> This signal is emitted with the <em>msg</em> and <em>data</em> whenever the
 <a href="#receive">receive</a>() function gets incoming data.
 
-<h3 class=fn>bool <a name="send"></a>TQCopChannel::send ( const&nbsp;<a href="qcstring.html">TQCString</a>&nbsp;&amp;&nbsp;channel, const&nbsp;<a href="qcstring.html">TQCString</a>&nbsp;&amp;&nbsp;msg, const&nbsp;<a href="qbytearray.html">TQByteArray</a>&nbsp;&amp;&nbsp;data )<tt> [static]</tt>
+<h3 class=fn>bool <a name="send"></a>TQCopChannel::send ( const&nbsp;<a href="ntqcstring.html">TQCString</a>&nbsp;&amp;&nbsp;channel, const&nbsp;<a href="ntqcstring.html">TQCString</a>&nbsp;&amp;&nbsp;msg, const&nbsp;<a href="qbytearray.html">TQByteArray</a>&nbsp;&amp;&nbsp;data )<tt> [static]</tt>
 </h3>
 Send the message <em>msg</em> on channel <em>channel</em> with data <em>data</em>.
 The message will be distributed to all clients subscribed to the
 channel.
-<p> Note that <a href="qdatastream.html">TQDataStream</a> provides a convenient way to fill the byte
+<p> Note that <a href="ntqdatastream.html">TQDataStream</a> provides a convenient way to fill the byte
 array with auxiliary data.
 <p> Example:
 <pre>
     <a href="qbytearray.html">TQByteArray</a> ba;
-    <a href="qdatastream.html">TQDataStream</a> stream( ba, <a href="qfile.html#open">IO_WriteOnly</a> );
+    <a href="ntqdatastream.html">TQDataStream</a> stream( ba, <a href="ntqfile.html#open">IO_WriteOnly</a> );
     stream &lt;&lt; TQString("cat") &lt;&lt; TQString("file.txt");
     TQCopChannel::<a href="#send">send</a>( "System/Shell", "execute(TQString,TQString)", ba );
     </pre>
@@ -158,7 +158,7 @@ requirement. Whatever convention you use the sender and receiver
 <em>must</em> agree on the argument types.
 <p> <p>See also <a href="#receive">receive</a>().
 
-<h3 class=fn>bool <a name="send-2"></a>TQCopChannel::send ( const&nbsp;<a href="qcstring.html">TQCString</a>&nbsp;&amp;&nbsp;channel, const&nbsp;<a href="qcstring.html">TQCString</a>&nbsp;&amp;&nbsp;msg )<tt> [static]</tt>
+<h3 class=fn>bool <a name="send-2"></a>TQCopChannel::send ( const&nbsp;<a href="ntqcstring.html">TQCString</a>&nbsp;&amp;&nbsp;channel, const&nbsp;<a href="ntqcstring.html">TQCString</a>&nbsp;&amp;&nbsp;msg )<tt> [static]</tt>
 </h3>
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 <p> Send the message <em>msg</em> on channel <em>channel</em>. The message will be