Rename ntqwidget* related files to equivalent tqwidget*

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

1 files changed, 8 insertions, 8 deletions

diff --git a/doc/html/focus.html b/doc/html/focus.html
index ed04ba415..7ab9b64ef 100644
--- a/doc/html/focus.html
+++ b/doc/html/focus.html
@@ -70,9 +70,9 @@ other. The order in which Tab presses move from widget to widget is
 called the tab order.
 <p> In TQt, this list is kept in the <a href="ntqfocusdata.html">TQFocusData</a> class. There is one
 <a href="ntqfocusdata.html">TQFocusData</a> object per window, and widgets automatically append
-themselves to the end of it when <a href="ntqwidget.html#setFocusPolicy">TQWidget::setFocusPolicy</a>() is
-called with an appropriate <a href="ntqwidget.html#FocusPolicy-enum">TQWidget::FocusPolicy</a>. You can customize
-the tab order using <a href="ntqwidget.html#setTabOrder">TQWidget::setTabOrder</a>(). (If you don't, Tab
+themselves to the end of it when <a href="tqwidget.html#setFocusPolicy">TQWidget::setFocusPolicy</a>() is
+called with an appropriate <a href="tqwidget.html#FocusPolicy-enum">TQWidget::FocusPolicy</a>. You can customize
+the tab order using <a href="tqwidget.html#setTabOrder">TQWidget::setTabOrder</a>(). (If you don't, Tab
 generally moves focus in the order of widget construction.) <a href="designer-manual.html">TQt Designer</a> provides a means of visually
 changing the tab order.
 <p> Since pressing Tab is so common, most widgets that can have focus
@@ -96,8 +96,8 @@ focus to this field.
 <p> Another exception to Tab support is text-entry widgets that must
 support the insertion of tabs; almost all text editors fall into this
 class. TQt treats Control+Tab as Tab and Control+Shift+Tab as
-Shift+Tab, and such widgets can reimplement <a href="ntqwidget.html#event">TQWidget::event</a>() and
-handle Tab before calling <a href="ntqwidget.html#event">TQWidget::event</a>() to get normal processing of
+Shift+Tab, and such widgets can reimplement <a href="tqwidget.html#event">TQWidget::event</a>() and
+handle Tab before calling <a href="tqwidget.html#event">TQWidget::event</a>() to get normal processing of
 all other keys. However, since some systems use Control+Tab for other
 purposes, and many users aren't aware of Control+Tab anyway, this
 isn't a complete solution.
@@ -121,7 +121,7 @@ it move to the 'B' button?
 entry, and to avoid it for most widgets where a mouse click has a
 different effect. (For buttons, we also recommend adding a keyboard
 shortcut: <a href="ntqbutton.html">TQButton</a> and its subclasses make this very easy.)
-<p> In TQt, only the <a href="ntqwidget.html#setFocusPolicy">TQWidget::setFocusPolicy</a>() function affects
+<p> In TQt, only the <a href="tqwidget.html#setFocusPolicy">TQWidget::setFocusPolicy</a>() function affects
 click-to-focus.
 <p> <h3> The user presses a keyboard shortcut.
 </h3>
@@ -153,8 +153,8 @@ the window should receive the focus.
 the last widget to have focus should regain it. TQt does this
 automatically.
 <p> If focus has never been in this window before and you know where focus
-should start out, call <a href="ntqwidget.html#setFocus">TQWidget::setFocus</a>() on the widget which
-should receive focus before you <a href="ntqwidget.html#show">TQWidget::show</a>() it. If you don't,
+should start out, call <a href="tqwidget.html#setFocus">TQWidget::setFocus</a>() on the widget which
+should receive focus before you <a href="tqwidget.html#show">TQWidget::show</a>() it. If you don't,
 TQt will pick a suitable widget.
 <p> 
 <!-- eof -->