1 files changed, 8 insertions, 8 deletions
diff --git a/doc/html/designer-manual-9.html b/doc/html/designer-manual-9.html
index ac66684e3..d87a9451c 100644
--- a/doc/html/designer-manual-9.html
+++ b/doc/html/designer-manual-9.html
@@ -111,7 +111,7 @@ body { background: #ffffff; color: black; }
 <p>If you wish to delete the add-in remove it from the toolbar then delete the<!-- index qmsdev.dll --> <tt>qmsdev.dll</tt> file from the add-ins directory.</p>
 <h4><a name="3-1"></a>Creating Makefiles without qmake</h4>
 <!-- index Makefiles --><p>The <tt>qmake</tt> tool provided with TQt can create Makefiles appropriate to your platform based on<!-- index .pro --> <tt>.pro</tt> project files. This section describes the dependencies involved in building a TQt application and gives a couple of simple example Makefiles. This section assumes that you have a good understanding of Makefiles.</p>
-<!-- index Macros!Q_OBJECT --><!-- index Q_OBJECT --><p><em>TQt Designer</em> produces<!-- index .ui --> <tt>.ui</tt> files which are used to generate<!-- index .h --> <tt>.h</tt> and<!-- index .cpp --> <tt>.cpp</tt> files for the compiler to compile. The<!-- index .ui --> <tt>.ui</tt> files are processed by <tt>uic</tt>. Classes which inherit from <a href="qobject.html">TQObject</a>, e.g. those which use slots and signals, require an additional<!-- index .cpp --> <tt>.cpp</tt> file to be generated. These files are generated by the <tt>moc</tt> and are named '<em>moc_</em>file.cpp' where the original<!-- index .cpp --> <tt>.cpp</tt> file is called 'file.cpp'. If your<!-- index .cpp --> <tt>.cpp</tt> file contains the <tt>Q_OBJECT</tt> macro an additional file 'file.moc' should be generated which must be <tt>#include</tt>d in the<!-- index .cpp --> <tt>.cpp</tt>, normally at the end. This requires an extra dependency being created.</p>
+<!-- index Macros!Q_OBJECT --><!-- index Q_OBJECT --><p><em>TQt Designer</em> produces<!-- index .ui --> <tt>.ui</tt> files which are used to generate<!-- index .h --> <tt>.h</tt> and<!-- index .cpp --> <tt>.cpp</tt> files for the compiler to compile. The<!-- index .ui --> <tt>.ui</tt> files are processed by <tt>uic</tt>. Classes which inherit from <a href="ntqobject.html">TQObject</a>, e.g. those which use slots and signals, require an additional<!-- index .cpp --> <tt>.cpp</tt> file to be generated. These files are generated by the <tt>moc</tt> and are named '<em>moc_</em>file.cpp' where the original<!-- index .cpp --> <tt>.cpp</tt> file is called 'file.cpp'. If your<!-- index .cpp --> <tt>.cpp</tt> file contains the <tt>Q_OBJECT</tt> macro an additional file 'file.moc' should be generated which must be <tt>#include</tt>d in the<!-- index .cpp --> <tt>.cpp</tt>, normally at the end. This requires an extra dependency being created.</p>
 <p>Processing<!-- index .ui --> <tt>.ui</tt> files with <tt>uic</tt> is done <em>twice</em>:</p>
 <pre>
 uic myform.ui -o myform.h
@@ -125,7 +125,7 @@ uic -subdecl Form formbase.h formbase.ui -o form.h
 uic -subimpl Form form.h formbase.ui -o form.cpp
 </pre>
 <p>First we generate the header and implementation file for our base class. Then we generate the header and implementation skeletons for our subclass. Note that the use of <tt>uic</tt> to generate skeletons is not something that would be done in a Makefile, we mention it here because it can be useful for command line users. Note also that the command line for <tt>-subdecl</tt> and for <tt>-subimpl</tt> are subtly different.</p>
-<p>For implementation files that contain classes which inherit from <a href="qobject.html">TQObject</a> we must create moc files:</p>
+<p>For implementation files that contain classes which inherit from <a href="ntqobject.html">TQObject</a> we must create moc files:</p>
 <pre>
 moc myform.h -o moc_myform.cpp
 </pre>
@@ -193,16 +193,16 @@ myform.h: myform.ui
 <p>Although Glade does not target TQt, the layout system and the widget set of GTK+ are similar to those of TQt, so the filter will retain most of the information in the<!-- index .glade --> <tt>.glade</tt> file.</p>
 <p>There are some considerations regarding the conversion of Glade files, as listed below:</p>
 <ul><li><p>Ampersands (&amp;) in labels</p>
-<p>TQt displays an ampersand when a <a href="qlabel.html">TQLabel</a> has no buddy. (A buddy is a widget that accepts focus on behalf of a <a href="qlabel.html">TQLabel</a>.) Glade allows GtkLabel widgets with an (underlined) accelerator key but with no buddy. This is an error since users expect underlined characters to be accelerators. In this situation, TQt displays the ampersand itself instead of underlining the accelerator key. You should go over these <a href="qlabel.html">TQLabel</a> widgets and set their "<em>buddy</em>" property.</p>
+<p>TQt displays an ampersand when a <a href="ntqlabel.html">TQLabel</a> has no buddy. (A buddy is a widget that accepts focus on behalf of a <a href="ntqlabel.html">TQLabel</a>.) Glade allows GtkLabel widgets with an (underlined) accelerator key but with no buddy. This is an error since users expect underlined characters to be accelerators. In this situation, TQt displays the ampersand itself instead of underlining the accelerator key. You should go over these <a href="ntqlabel.html">TQLabel</a> widgets and set their "<em>buddy</em>" property.</p>
 <li><p>Layout placeholders</p>
-<p>GTK allows a layout position to be occupied by a placeholder. <em>TQt Designer</em> converts those placeholders into <a href="qlabel.html">TQLabel</a>s whose text is "?" in red, so that you can find them and fix them manually.</p>
+<p>GTK allows a layout position to be occupied by a placeholder. <em>TQt Designer</em> converts those placeholders into <a href="ntqlabel.html">TQLabel</a>s whose text is "?" in red, so that you can find them and fix them manually.</p>
 <li><p>GTK+ or GNOME widget with no TQt equivalent</p>
-<p>TQt has equivalents for most GTK+ widgets, but Glade also supports GNOME, whose goal is to provide a complete desktop environment. Because TQt's scope is narrower, when <em>TQt Designer</em> encounters a widget it cannot convert, it replaces it with a label that indicates the problem. For example, a GnomePaperSelector will be replaced by a <a href="qlabel.html">TQLabel</a> whose text is "GnomePaperSelector?" in red. If you are porting to KDE, you might want to use the corresponding KDE widget.</p>
-<p>Other GTK+/GNOME widgets are only supported in certain contexts. For example, the GnomeDruid can be embedded in another widget, whereas the corresponding <a href="qwizard.html">TQWizard</a> class cannot.</p>
+<p>TQt has equivalents for most GTK+ widgets, but Glade also supports GNOME, whose goal is to provide a complete desktop environment. Because TQt's scope is narrower, when <em>TQt Designer</em> encounters a widget it cannot convert, it replaces it with a label that indicates the problem. For example, a GnomePaperSelector will be replaced by a <a href="ntqlabel.html">TQLabel</a> whose text is "GnomePaperSelector?" in red. If you are porting to KDE, you might want to use the corresponding KDE widget.</p>
+<p>Other GTK+/GNOME widgets are only supported in certain contexts. For example, the GnomeDruid can be embedded in another widget, whereas the corresponding <a href="ntqwizard.html">TQWizard</a> class cannot.</p>
 <li><p>Message boxes and other high-level dialogs</p>
-<p>Glade supports editing of GnomeMessageBox, GtkFileSelection, GtkFontSelectionDialog and others. This is trivially achieved in TQt by means of a <a href="qmessagebox.html">TQMessageBox</a> dialog, a <a href="qfiledialog.html">TQFileDialog</a>, a <a href="qfontdialog.html">TQFontDialog</a>, etc., in C++ code.</p>
+<p>Glade supports editing of GnomeMessageBox, GtkFileSelection, GtkFontSelectionDialog and others. This is trivially achieved in TQt by means of a <a href="ntqmessagebox.html">TQMessageBox</a> dialog, a <a href="ntqfiledialog.html">TQFileDialog</a>, a <a href="ntqfontdialog.html">TQFontDialog</a>, etc., in C++ code.</p>
 <li><p>Stand-alone popup menus</p>
-<p><em>TQt Designer</em> only supports popup menus inside a <a href="qmainwindow.html">TQMainWindow</a>. If you need a stand-alone popup menu (presumably a context menu), you can easily write code that does this using <a href="qpopupmenu.html">TQPopupMenu</a>.</p>
+<p><em>TQt Designer</em> only supports popup menus inside a <a href="ntqmainwindow.html">TQMainWindow</a>. If you need a stand-alone popup menu (presumably a context menu), you can easily write code that does this using <a href="ntqpopupmenu.html">TQPopupMenu</a>.</p>
 <li><p>Size policy parameters</p>
 <p>Glade provides size policies in the "Place" tab of the property editor. <em>TQt Designer</em> does not attempt to make use of the padding, expand, shrink and fill information, as the TQt defaults are usually good enough. In a few cases, you might have to set the "<em>sizePolicy</em>" property manually to obtain the effect you want.</p>
 <li><p>GNOME standard icons</p>