Rename style nt* related files to equivalent tq*

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

1 files changed, 6 insertions, 6 deletions

diff --git a/doc/html/motif-walkthrough-5.html b/doc/html/motif-walkthrough-5.html
index d6ad1178e..31b1aebf9 100644
--- a/doc/html/motif-walkthrough-5.html
+++ b/doc/html/motif-walkthrough-5.html
@@ -41,7 +41,7 @@ have converted the <em>View</em> widget.  The <em>Print</em> dialog will be
 removed once we have finished our migration, since we will use
 <a href="tqprinter.html">TQPrinter</a> instead.  Based on this information, we decide that it is not
 worth replacing the <em>Print</em> dialog with a custom <a href="tqdialog.html">TQDialog</a> replacement.
-Instead, we will keep the <a href="motif-extension.html#Motif">Motif</a> based dialog and use <a href="qmotifdialog.html">TQMotifDialog</a> to
+Instead, we will keep the <a href="motif-extension.html#Motif">Motif</a> based dialog and use <a href="tqmotifdialog.html">TQMotifDialog</a> to
 integrate the dialog with the application.
 <p> <h2> Modality Requirements
 </h2>
@@ -74,7 +74,7 @@ function:
 <p> <pre></pre>
 <p> <h2> Integrating the <em>Print</em> Dialog
 </h2>
-<a name="2"></a><p> Now that the <em>Print</em> dialog has the appropriate <em>accept</em> and <em>reject</em> callbacks, we can use <a href="qmotifdialog.html">TQMotifDialog</a>.  First we need to include
+<a name="2"></a><p> Now that the <em>Print</em> dialog has the appropriate <em>accept</em> and <em>reject</em> callbacks, we can use <a href="tqmotifdialog.html">TQMotifDialog</a>.  First we need to include
 the TQMotifDialog header in <tt>todo.cpp</tt>.
 <p> 
 
@@ -82,19 +82,19 @@ the TQMotifDialog header in <tt>todo.cpp</tt>.
 <p> We add a <tt>ShowPrintDialog()</tt> function which will create and execute the
 print dialog.
 <p> <pre></pre>
-<p> We change the <em>Print</em> menu item callback to call the new <tt>ShowPrintDialog()</tt> function.  We pass the top-level <a href="qmotifwidget.html">TQMotifWidget</a>, which
+<p> We change the <em>Print</em> menu item callback to call the new <tt>ShowPrintDialog()</tt> function.  We pass the top-level <a href="tqmotifwidget.html">TQMotifWidget</a>, which
 we will use as the parent for the dialog.
 <p> <pre></pre>
 <p> The <tt>ShowPrintDialog()</tt> function creates the <em>Print</em> dialog and
 executes it.  We use the <tt>XmdNprintCallback</tt> callback to accept the
 dialog and the <tt>XmNcancelCallback</tt> callback to reject the dialog.  We
-can do this easily by using the <a href="qmotifdialog.html#acceptCallback">TQMotifDialog::acceptCallback</a>() and
-<a href="qmotifdialog.html#rejectCallback">TQMotifDialog::rejectCallback</a>() functions, respectively.  We also
+can do this easily by using the <a href="tqmotifdialog.html#acceptCallback">TQMotifDialog::acceptCallback</a>() and
+<a href="tqmotifdialog.html#rejectCallback">TQMotifDialog::rejectCallback</a>() functions, respectively.  We also
 ensure that the <em>print</em> callback continues to call the <tt>Print()</tt> function as before.
 <p> <pre></pre>
 <p> After we build the project, the application runs and operates as
 expected.  There is no visual or behavioral difference, even though
-the <em>Print</em> dialog is using <a href="qmotifdialog.html">TQMotifDialog</a>.
+the <em>Print</em> dialog is using <a href="tqmotifdialog.html">TQMotifDialog</a>.
 <p> [ <a href="motif-walkthrough-4.html">Previous: Using Custom TQDialogs</a> ]
 [ <a href="motif-walkthrough.html">Home</a> ]
 [ <a href="motif-walkthrough-6.html">Next: Using TQt Main Window Classes</a> ]