Update to latest tqt3 automated conversion

1 files changed, 34 insertions, 34 deletions

diff --git a/doc/html/qaxserver.html b/doc/html/qaxserver.html
index ad20e4c48..514651198 100644
--- a/doc/html/qaxserver.html
+++ b/doc/html/qaxserver.html
@@ -143,7 +143,7 @@ body { background: #ffffff; color: black; }
 <a name="1"></a><p> The TQAxServer module provides a static library implementing the
 functions required to turn a standard TQt binary into an ActiveX
 control server. 
-<p> This module is part of the <a href="activeqt.html">ActiveTQt
+<p> This module is part of the <a href="activentqt.html">ActiveTQt
     framework</a>. (To incorporate ActiveX controls in a TQt
 application see the <a href="qaxcontainer.html">TQAxContainer
     module</a>.) 
@@ -264,7 +264,7 @@ implement a custom factory that doesn't require one.
 macro, the <a href="qaxfactory.html">TQAxFactory</a> subclass had no appropriate constructor.
 Provide a public class constructor like
 <pre>
-    MyFactory( const <a href="quuid.html">TQUuid</a> &amp;, const <a href="quuid.html">TQUuid</a> &amp; );
+    MyFactory( const <a href="ntquuid.html">TQUuid</a> &amp;, const <a href="ntquuid.html">TQUuid</a> &amp; );
     </pre>
  
 for your factory class.
@@ -296,7 +296,7 @@ manager to kill the process (e.g. when a client doesn't release
 the controls properly).
 <p> <h4> Postprocessing and runtime errors
 </h4>
-<a name="4-1-3"></a><p> The <a href="activeqt.html#ActiveTQt">ActiveTQt</a> build system performs four commands after the linking
+<a name="4-1-3"></a><p> The <a href="activentqt.html#ActiveTQt">ActiveTQt</a> build system performs four commands after the linking
 of the binary to make it into an ActiveX server.
 <p> <ul>
 <li> Call the server to dump the IDL for the controls
@@ -306,7 +306,7 @@ of the binary to make it into an ActiveX server.
 </ul>
 <p> For this to work the server has to meet some requirements:
 <p> <ul>
-<li> All controls exposed can be created with nothing but a <a href="qapplication.html">TQApplication</a>
+<li> All controls exposed can be created with nothing but a <a href="ntqapplication.html">TQApplication</a>
 instance being present
 <li> The initial linking of the server includes a temporary type 
 library resource
@@ -376,12 +376,12 @@ will use the existing process for the next client trying to create
 an ActiveX control.
 <p> <h2> Implementing Controls
 </h2>
-<a name="5"></a><p> To implement an ActiveX control with TQt, create a subclass of <a href="qwidget.html">TQWidget</a>
+<a name="5"></a><p> To implement an ActiveX control with TQt, create a subclass of <a href="ntqwidget.html">TQWidget</a>
 or any existing TQWidget subclass:
 <p> <pre>
-    #include &lt;<a href="qwidget-h.html">qwidget.h</a>&gt;
+    #include &lt;<a href="qwidget-h.html">ntqwidget.h</a>&gt;
 
-    class MyActiveX : public <a href="qwidget.html">TQWidget</a>
+    class MyActiveX : public <a href="ntqwidget.html">TQWidget</a>
     {
         <a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a>
     </pre>
@@ -398,7 +398,7 @@ and functions, signals and slots like any normal TQWidget.
 <a href="#footnote1"><sup>(1)</sup></a><a name="footnote-call1"></a> 
 <p> <pre>
     public:
-        MyActiveX( <a href="qwidget.html">TQWidget</a> *parent = 0, const char *name = 0 )
+        MyActiveX( <a href="ntqwidget.html">TQWidget</a> *parent = 0, const char *name = 0 )
         ...
         
         int value() const;
@@ -502,13 +502,13 @@ slots are:
 <td valign="top">bool&
 <td valign="top">[in, out] VARIANT_BOOL*
 <tr bgcolor="#d0d0d0">
-<td valign="top">TQString, const <a href="qstring.html">TQString</a>&
+<td valign="top">TQString, const <a href="ntqstring.html">TQString</a>&
 <td valign="top">[in] BSTR
 <tr bgcolor="#f0f0f0">
 <td valign="top">TQString&
 <td valign="top">[in, out] BSTR*
 <tr bgcolor="#d0d0d0">
-<td valign="top">TQCString, const <a href="qcstring.html">TQCString</a>&
+<td valign="top">TQCString, const <a href="ntqcstring.html">TQCString</a>&
 <td valign="top">[in] BSTR
 <tr bgcolor="#f0f0f0">
 <td valign="top">TQString&
@@ -532,7 +532,7 @@ slots are:
 <td valign="top">double&
 <td valign="top">[in, out] double*
 <tr bgcolor="#d0d0d0">
-<td valign="top">TQColor, const <a href="qcolor.html">TQColor</a>&
+<td valign="top">TQColor, const <a href="ntqcolor.html">TQColor</a>&
 <td valign="top">[in] OLE_COLOR
 <tr bgcolor="#f0f0f0">
 <td valign="top">TQColor&
@@ -544,31 +544,31 @@ slots are:
 <td valign="top">TQDate&
 <td valign="top">[in, out] DATE*
 <tr bgcolor="#d0d0d0">
-<td valign="top">TQDateTime, const <a href="qdatetime.html">TQDateTime</a>&
+<td valign="top">TQDateTime, const <a href="ntqdatetime.html">TQDateTime</a>&
 <td valign="top">[in] DATE
 <tr bgcolor="#f0f0f0">
 <td valign="top">TQDateTime&
 <td valign="top">[in, out] DATE*
 <tr bgcolor="#d0d0d0">
-<td valign="top">TQFont, const <a href="qfont.html">TQFont</a>&
+<td valign="top">TQFont, const <a href="ntqfont.html">TQFont</a>&
 <td valign="top">[in] IFontDisp*
 <tr bgcolor="#f0f0f0">
 <td valign="top">TQFont&
 <td valign="top">[in, out] IFontDisp**
 <tr bgcolor="#d0d0d0">
-<td valign="top">TQPixmap, const <a href="qpixmap.html">TQPixmap</a>&
+<td valign="top">TQPixmap, const <a href="ntqpixmap.html">TQPixmap</a>&
 <td valign="top">[in] IPictureDisp*
 <tr bgcolor="#f0f0f0">
 <td valign="top">TQPixmap&
 <td valign="top">[in, out] IPictureDisp**
 <tr bgcolor="#d0d0d0">
-<td valign="top">TQValueList&lt;TQVariant&gt;, const <a href="qvaluelist.html">TQValueList</a>&lt;TQVariant&gt;&
+<td valign="top">TQValueList&lt;TQVariant&gt;, const <a href="ntqvaluelist.html">TQValueList</a>&lt;TQVariant&gt;&
 <td valign="top">[in] SAFEARRAY(VARIANT)
 <tr bgcolor="#f0f0f0">
 <td valign="top">TQValueList&lt;TQVariant&gt;&
 <td valign="top">[in, out] SAFEARRAY(VARIANT)*
 <tr bgcolor="#d0d0d0">
-<td valign="top">TQStringList, const <a href="qstringlist.html">TQStringList</a>&
+<td valign="top">TQStringList, const <a href="ntqstringlist.html">TQStringList</a>&
 <td valign="top">[in] SAFEARRAY(BSTR)
 <tr bgcolor="#f0f0f0">
 <td valign="top">TQStringList&
@@ -585,13 +585,13 @@ slots are:
 <tr bgcolor="#f0f0f0">
 <td valign="top">TQRect&
 <a href="#footnote3"><sup>(3)</sup></a><a name="footnote-call3"></a> 
-<td valign="top">[in, out] struct <a href="qrect.html">TQRect</a> (user defined)
+<td valign="top">[in, out] struct <a href="ntqrect.html">TQRect</a> (user defined)
 <tr bgcolor="#d0d0d0">
 <td valign="top">TQSize&
-<td valign="top">[in, out] struct <a href="qsize.html">TQSize</a> (user defined)
+<td valign="top">[in, out] struct <a href="ntqsize.html">TQSize</a> (user defined)
 <tr bgcolor="#f0f0f0">
 <td valign="top">TQPoint&
-<td valign="top">[in, out] struct <a href="qpoint.html">TQPoint</a> (user defined)
+<td valign="top">[in, out] struct <a href="ntqpoint.html">TQPoint</a> (user defined)
 </table></center>
 <p> Also supported are exported enums and sets (see Q_ENUMS and Q_SETS).
 The in-parameter types are also supported as return values.
@@ -602,7 +602,7 @@ data types are ignored by the TQActiveX framework.
 <a name="5-2"></a><p> COM objects can have multiple sub-objects that can represent a sub element
 of the COM object. A COM object representing a multi-document spread sheet 
 application can for example provide one sub-object for each spread sheet.
-<p> Any <a href="qobject.html">TQObject</a> subclass can be used as the type for a sub object in ActiveX. The
+<p> Any <a href="ntqobject.html">TQObject</a> subclass can be used as the type for a sub object in ActiveX. The
 <a href="qaxfactory.html">TQAxFactory</a> implementation (see below) needs to return the classname of the
 sub type as one key in the featureList() implementation, as well as the IDs 
 for the COM class, the interface and event interface of that type. Then the
@@ -613,10 +613,10 @@ type can be used as e.g. the return value or paramter of a slot.
 inheritance from the <a href="qaxbindable.html">TQAxBindable</a> class:
 <p> 
     <pre>
-    #include &lt;qwidget.h&gt;
+    #include &lt;ntqwidget.h&gt;
     <b>#include &lt;qaxbindable.h&gt;</b>
 
-    class MyActiveX : public <a href="qwidget.html">TQWidget</a><b>, public TQAxBindable</b>
+    class MyActiveX : public <a href="ntqwidget.html">TQWidget</a><b>, public TQAxBindable</b>
     {
         Q_OBJECT
     </pre>
@@ -654,7 +654,7 @@ the ActiveX control on the target system:
 <p> The <a href="qaxfactory.html">TQAxFactory class documentation</a> explains 
 how to use this macro, and how to implement and use custom factories.
 <p> For out-of-process executable servers you can implement a main()
-function to instantiate a <a href="qapplication.html">TQApplication</a> object and enter the event
+function to instantiate a <a href="ntqapplication.html">TQApplication</a> object and enter the event
 loop just like any normal TQt application. By default the
 application will start as a standard TQt application, but if you
 pass <tt>-activex</tt> on the command line it will start as an ActiveX
@@ -662,7 +662,7 @@ server. Use <a href="qaxfactory.html#isServer">TQAxFactory::isServer</a>() to cr
 application interface, or to prevent a stand-alone execution:
 <p> 
     <pre>
-    #include &lt;qapplication.h&gt;
+    #include &lt;ntqapplication.h&gt;
     <b>#include &lt;qaxfactory.h&gt;</b>
 
     int main( int argc, char **argv )
@@ -815,13 +815,13 @@ following client applications.
 </h3>
 <a name="8-1"></a><p> By default all ActiveX controls expose not only their own methods
 and properties to ActiveX clients, but also those of all super
-classes, including <a href="qwidget.html">TQWidget</a>.
+classes, including <a href="ntqwidget.html">TQWidget</a>.
 <p> This can be controlled by reimplementing <a href="qaxfactory.html">TQAxFactory</a>'s
 exposeToSuperClass() function. Reimplement the function to return
 the last (furthest up the inheritance hierarchy) super class that
 should be exposed:
 <p> <pre>
-    TQString MyFactory::exposeToSuperClass( const <a href="qstring.html">TQString</a> &amp;key ) const
+    TQString MyFactory::exposeToSuperClass( const <a href="ntqstring.html">TQString</a> &amp;key ) const
     {
         if ( key == "SmallActiveX" )
             return key;
@@ -912,7 +912,7 @@ own API, and is available in the "Insert Objects" dialog of Microsoft
 Office applications.
 <p> 
     <pre>
-    class MyActiveX : public <a href="qwidget.html">TQWidget</a>
+    class MyActiveX : public <a href="ntqwidget.html">TQWidget</a>
     {
         Q_OBJECT
         <b>Q_CLASSINFO("Version", "2.0")
@@ -943,7 +943,7 @@ control is supposed to run needs to be licensed.
 macro.
 
     <pre>
-    class MyLicensedControl : public <a href="qwidget.html">TQWidget</a>
+    class MyLicensedControl : public <a href="ntqwidget.html">TQWidget</a>
     {
         Q_OBJECT
         <b>Q_CLASSINFO("LicenseKey", "&lt;key string&gt;")</b>
@@ -974,7 +974,7 @@ to subclass additional COM interface classes.
     public:
         AxImpl() {}
 
-        long queryInterface( const <a href="quuid.html">TQUuid</a> &amp;iid, void **iface );
+        long queryInterface( const <a href="ntquuid.html">TQUuid</a> &amp;iid, void **iface );
 
         // IUnknown
         TQAXAGG_IUNKNOWN
@@ -987,7 +987,7 @@ to subclass additional COM interface classes.
 <p> Reimplement the <tt>queryInterface()</tt> function to support the additional 
 COM interfaces.
 <p> <pre>
-    long AxImpl::queryInterface( const <a href="quuid.html">TQUuid</a> &amp;iid, void **iface )
+    long AxImpl::queryInterface( const <a href="ntquuid.html">TQUuid</a> &amp;iid, void **iface )
     {
         *iface = 0;
         if ( iid == IID_ISomeCOMInterface )
@@ -1015,12 +1015,12 @@ interface pointer returned by the controllingUnknown() function, e.g.
 Do not support the <tt>IUnknown</tt> interface itself in your <tt>queryInterface()</tt> 
 implementation.
 <p> Implement the methods of the COM interfaces, and use TQAxAggregated::Object()
-if you need to make calls to the <a href="qobject.html">TQObject</a> subclass implementing the control.
+if you need to make calls to the <a href="ntqobject.html">TQObject</a> subclass implementing the control.
 <p> In your <a href="qaxbindable.html">TQAxBindable</a> subclass, implement <tt>createAggregate()</tt> to return
 a new object of the <a href="qaxaggregated.html">TQAxAggregated</a> subclass.
 <p> 
     <pre>
-    class MyActiveX : public <a href="qwidget.html">TQWidget</a>,                       
+    class MyActiveX : public <a href="ntqwidget.html">TQWidget</a>,                       
                       <b>public TQAxBindable</b>
     {
     	Q_OBJECT
@@ -1046,7 +1046,7 @@ your implementation of TQAxFactory::create.
  <a href="#footnote-call1">Back...</a> <li><a name="footnote2"></a>
 
 COM cannot marshal IPictureDisp accross process boundaries,
-so <a href="qpixmap.html">TQPixmap</a> properties cannot be called for out-of-process servers. You
+so <a href="ntqpixmap.html">TQPixmap</a> properties cannot be called for out-of-process servers. You
 can however marshal the image data via e.g. temporary files. See the
 Microsoft 
 <a href="http://support.microsoft.com/default.aspx?scid=kb;[LN];Q150034">KB article 
@@ -1055,7 +1055,7 @@ Microsoft
 
 OLE needs to marshal user defined types by reference (ByRef), and cannot 
 marshal them by value (ByVal). This is why const-references and object
-parameters are not supported for <a href="qrect.html">TQRect</a>, <a href="qsize.html">TQSize</a> and <a href="qpoint.html">TQPoint</a>. Also note that
+parameters are not supported for <a href="ntqrect.html">TQRect</a>, <a href="ntqsize.html">TQSize</a> and <a href="ntqpoint.html">TQPoint</a>. Also note that
 servers with this datatype require Windows 98 or DCOM 1.2 to be installed.
  <a href="#footnote-call3">Back...</a> <li><a name="footnote4"></a>