Update to latest tqt3 automated conversion

1 files changed, 12 insertions, 12 deletions

diff --git a/doc/html/designer-manual-16.html b/doc/html/designer-manual-16.html
index df37d5e9..be3536c7 100644
--- a/doc/html/designer-manual-16.html
+++ b/doc/html/designer-manual-16.html
@@ -32,7 +32,7 @@ body { background: #ffffff; color: black; }
 <td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><p align="right">[<a href="designer-manual-15.html">Prev: Reference: Windows</a>] [<a href="designer-manual.html">Home</a>]</p>
 <h2 align="center">Reference: The .ui File Format</h2>
 <p><em>TQt Designer</em> stores forms in <tt>.ui</tt> files. These files use an XML format to represent form elements and their characteristics. This document provides an overview of the XML format used, and should provide enough information for developers to write their own <tt>.ui</tt> parsers so that they can read and modify <tt>.ui</tt> files programatically.</p>
-<p>One way to parse a <tt>.ui</tt> file is to use TQt and the <a href="qdomdocument.html">TQDomDocument</a> class; this is how <em>TQt Designer</em> does it: see the <tt>uilib/qwidgetfactory.h</tt> and <tt>uilib/qwidgetfactory.cpp</tt> source files. For information on dynamically loading and running <tt>.ui</tt> files see <a href="designer-manual-6.html#2-3-2">Loading and Executing a Dynamic Dialog</a>.</p>
+<p>One way to parse a <tt>.ui</tt> file is to use TQt and the <a href="qdomdocument.html">TQDomDocument</a> class; this is how <em>TQt Designer</em> does it: see the <tt>uilib/ntqwidgetfactory.h</tt> and <tt>uilib/qwidgetfactory.cpp</tt> source files. For information on dynamically loading and running <tt>.ui</tt> files see <a href="designer-manual-6.html#2-3-2">Loading and Executing a Dynamic Dialog</a>.</p>
 <p>The doctype of a <tt>.ui</tt> file is simply "UI", so the doctype tag is:</p>
 <pre>
 &lt;!DOCTYPE UI&gt;
@@ -44,7 +44,7 @@ body { background: #ffffff; color: black; }
 &lt;/UI&gt;
 </pre>
 <p>Within the UI entity, there may one or zero of the following element types:</p>
-<ul><li><p><a href="designer-manual-16.html#1-1">actions</a> - actions, for <a href="qmainwindow.html">TQMainWindow</a> forms</p>
+<ul><li><p><a href="designer-manual-16.html#1-1">actions</a> - actions, for <a href="ntqmainwindow.html">TQMainWindow</a> forms</p>
 <li><p><a href="designer-manual-16.html#1-2">author</a> - the form's author</p>
 <li><p><a href="designer-manual-16.html#1-3">class</a> - the form's class name</p>
 <li><p><a href="designer-manual-16.html#1-4">comment</a> - comments, e.g. copyright notices</p>
@@ -57,13 +57,13 @@ body { background: #ffffff; color: black; }
 <li><p><a href="designer-manual-16.html#1-11">includes</a> - include files</p>
 <li><p><a href="designer-manual-16.html#1-12">layoutdefaults</a> - default values for layout attributes</p>
 <li><p><a href="designer-manual-16.html#1-13">layoutfunctions</a> - dynamic default values for layout attributes</p>
-<li><p><a href="designer-manual-16.html#1-14">menubar</a> - menu bar, for <a href="qmainwindow.html">TQMainWindow</a> forms</p>
+<li><p><a href="designer-manual-16.html#1-14">menubar</a> - menu bar, for <a href="ntqmainwindow.html">TQMainWindow</a> forms</p>
 <li><p><a href="designer-manual-16.html#1-15">pixmapfunction</a> - the name of the function to use for retrieving pixmaps if neither embedded nor external pixmaps are being used</p>
 <li><p><a href="designer-manual-16.html#1-16">pixmapinproject</a> - an element whose presence ndicates that the pixmaps are handled by the <tt>.pro</tt> file</p>
 <li><p><a href="designer-manual-16.html#1-17">signals</a> - signal declarations</p>
 <li><p><a href="designer-manual-16.html#1-18">slots</a> - slot declarations</p>
 <li><p><a href="designer-manual-16.html#1-19">tabstops</a> - the form's tab order</p>
-<li><p><a href="designer-manual-16.html#1-20">toolbars</a> - toolbars, for <a href="qmainwindow.html">TQMainWindow</a> forms</p>
+<li><p><a href="designer-manual-16.html#1-20">toolbars</a> - toolbars, for <a href="ntqmainwindow.html">TQMainWindow</a> forms</p>
 <li><p><a href="designer-manual-16.html#1-21">variables</a> - class variables</p>
 <li><p><a href="designer-manual-16.html#1-22">widget</a> - the form itself; this element may contain other elements, including other <tt>widget</tt> elements</p>
 <li><p><a href="designer-manual-16.html#1-23">forward</a> - TQt 3.x beta backwards compatibility</p>
@@ -72,7 +72,7 @@ body { background: #ffffff; color: black; }
 </ul><p>The ordering of elements is arbitrary, although it is common for the <a href="designer-manual-16.html#1-3">class</a> element to be first.</p>
 <h3><a name="1"></a>UI Elements</h3>
 <a name="actions"></a><h4><a name="1-1"></a>actions</h4>
-<p>This element is used to store the form's actions. It only occurs in <a href="qmainwindow.html">TQMainWindow</a> forms.</p>
+<p>This element is used to store the form's actions. It only occurs in <a href="ntqmainwindow.html">TQMainWindow</a> forms.</p>
 <p>The <tt>actions</tt> element contains one or more <tt>action</tt> elements. Each <tt>action</tt> element contains one or more properties. Each property has a <tt>name</tt> attribute, and a single value which is contained within a <a href="designer-manual-16.html#datatype">datatype</a> element.</p>
 <pre>
 &lt;actions&gt;
@@ -230,9 +230,9 @@ body { background: #ffffff; color: black; }
     &lt;include location="local" impldecl="in implementation"&gt;pixmapcollection.h&lt;/include&gt;
     &lt;include location="local" impldecl="in implementation"&gt;pixmapchooser.h&lt;/include&gt;
     &lt;include location="local" impldecl="in implementation"&gt;project.h&lt;/include&gt;
-    &lt;include location="global" impldecl="in implementation"&gt;qfileinfo.h&lt;/include&gt;
-    &lt;include location="global" impldecl="in implementation"&gt;qimage.h&lt;/include&gt;
-    &lt;include location="global" impldecl="in declaration"&gt;qpixmap.h&lt;/include&gt;
+    &lt;include location="global" impldecl="in implementation"&gt;ntqfileinfo.h&lt;/include&gt;
+    &lt;include location="global" impldecl="in implementation"&gt;ntqimage.h&lt;/include&gt;
+    &lt;include location="global" impldecl="in declaration"&gt;ntqpixmap.h&lt;/include&gt;
     &lt;include location="local" impldecl="in implementation"&gt;pixmapcollectioneditor.ui.h&lt;/include&gt;
 &lt;/includes&gt;
 </pre>
@@ -252,7 +252,7 @@ body { background: #ffffff; color: black; }
 <li><p>If no integer value is specified and a layout function is specified then the function is used.</p>
 <li><p>If no integer value or function is specified then the default value from <tt>layoutdefaults</tt> is used.</p>
 </ol><a name="menubar"></a><h4><a name="1-14"></a>menubar</h4>
-<p>Applications that use <a href="qmainwindow.html">TQMainWindow</a> often have a menubar. The menubar has a name property and one or more popup menu items. Each menu item has one or more actions and optionally separators.</p>
+<p>Applications that use <a href="ntqmainwindow.html">TQMainWindow</a> often have a menubar. The menubar has a name property and one or more popup menu items. Each menu item has one or more actions and optionally separators.</p>
 <pre>
 &lt;menubar&gt;
     &lt;property name="name"&gt;
@@ -306,7 +306,7 @@ body { background: #ffffff; color: black; }
 &lt;/tabstops&gt;
 </pre>
 <a name="toolbars"></a><h4><a name="1-20"></a>toolbars</h4>
-<p>Forms that have toolbars (dock windows) use the <tt>&lt;toolbars&gt;</tt> tag to hold the details. These forms are normally <a href="qmainwindow.html">TQMainWindow</a>s (or subclasses). Each toolbar has a dock attribute which identifies which dock window the toolbar initially belongs to. They also have both name and label properties. Each toolbar button is represented by an action. Toolbars can also hold other widgets, in which case the <tt>&lt;toolbar&gt;</tt> tag includes appropriate <tt>&lt;widget&gt;</tt> tags which give the class, name and any non-default property values for the relevant widget.</p>
+<p>Forms that have toolbars (dock windows) use the <tt>&lt;toolbars&gt;</tt> tag to hold the details. These forms are normally <a href="ntqmainwindow.html">TQMainWindow</a>s (or subclasses). Each toolbar has a dock attribute which identifies which dock window the toolbar initially belongs to. They also have both name and label properties. Each toolbar button is represented by an action. Toolbars can also hold other widgets, in which case the <tt>&lt;toolbar&gt;</tt> tag includes appropriate <tt>&lt;widget&gt;</tt> tags which give the class, name and any non-default property values for the relevant widget.</p>
 <pre>
 &lt;toolbars&gt;
     &lt;toolbar dock="2"&gt;
@@ -374,7 +374,7 @@ body { background: #ffffff; color: black; }
 </pre>
 <a name="widget"></a><h4><a name="1-22"></a>widget</h4>
 <p>Widgets are used at multiple levels within a <tt>.ui</tt> file. The whole form itself is a widget, and it contains other widgets, usually within the context of layouts such as hboxes, vboxes and grids.</p>
-<p>Below is an example of a complete <tt>.ui</tt> file. The form itself is a <a href="qwidget.html">TQWidget</a> with various non-default properties set. This widget contains a single hbox, which also has some non-default properties, and which contains a single <a href="qtextbrowser.html">TQTextBrowser</a> widget.</p>
+<p>Below is an example of a complete <tt>.ui</tt> file. The form itself is a <a href="ntqwidget.html">TQWidget</a> with various non-default properties set. This widget contains a single hbox, which also has some non-default properties, and which contains a single <a href="ntqtextbrowser.html">TQTextBrowser</a> widget.</p>
 <pre>
 &lt;!DOCTYPE UI&gt;&lt;UI version="3.1" stdsetdef="1"&gt;
 &lt;class&gt;WinIntroPage&lt;/class&gt;
@@ -456,7 +456,7 @@ body { background: #ffffff; color: black; }
 </pre>
 <li><p><tt>iconset</tt> - an iconset (see <tt>pixmap</tt>), e.g. <tt>&lt;iconset&gt;filenew&lt;/iconset&gt;</tt></p>
 <li><p><tt>number</tt> - an integer with an optional sign, e.g. <tt>&lt;number&gt;947&lt;/number&gt;</tt></p>
-<li><p><tt>palette</tt> - a <a href="qwidget.html#palette-prop">palette</a></p>
+<li><p><tt>palette</tt> - a <a href="ntqwidget.html#palette-prop">palette</a></p>
 <li><p><tt>pixmap</tt> - a pixmap, normally the name or "key" of the pixmap; the name is used if pixmaps are stored in the project, the key is used if a user defined function is used to access the pixmap. It is also possible for pixmaps to be included inline. Example: <tt>&lt;pixmap&gt;chair&lt;/pixmap&gt;</tt></p>
 <li><p><tt>point</tt> - a point, e.g. <tt>&lt;point&gt;&lt;x&gt;15&lt;/x&gt;&lt;y&gt;95&lt;/y&gt;&lt;/point&gt;</tt></p>
 <li><p><tt>rect</tt> - a rectangle, e.g.</p>