Rename ntqwidget* related files to equivalent tqwidget*

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

1 files changed, 4 insertions, 4 deletions

diff --git a/doc/html/eventsandfilters.html b/doc/html/eventsandfilters.html
index 668e11fe1..b891f4d1e 100644
--- a/doc/html/eventsandfilters.html
+++ b/doc/html/eventsandfilters.html
@@ -36,7 +36,7 @@ body { background: #ffffff; color: black; }
 <p> In TQt, an event is an object that inherits <a href="ntqevent.html">TQEvent</a>. Events are
 delivered to objects that inherit <a href="tqobject.html">TQObject</a> through calling <a href="tqobject.html#event">TQObject::event</a>(). Event delivery means that an event has occurred, the
 <a href="ntqevent.html">TQEvent</a> indicates precisely what, and the <a href="tqobject.html">TQObject</a> needs to respond. Most
-events are specific to <a href="ntqwidget.html">TQWidget</a> and its subclasses, but there are
+events are specific to <a href="tqwidget.html">TQWidget</a> and its subclasses, but there are
 important events that aren't related to graphics, for example, socket
 activation, which is the event used by <a href="ntqsocketnotifier.html">TQSocketNotifier</a> for its
 work.
@@ -57,7 +57,7 @@ event delivery mechanisms are flexible. The documentation for
 <a href="ntqapplication.html#notify">TQApplication::notify</a>() concisely tells the whole story, here we
 will explain enough for 99% of applications.
 <p> The normal way for an event to be delivered is by calling a virtual
-function. For example, <a href="qpaintevent.html">TQPaintEvent</a> is delivered by calling <a href="ntqwidget.html#paintEvent">TQWidget::paintEvent</a>(). This virtual function is responsible for
+function. For example, <a href="qpaintevent.html">TQPaintEvent</a> is delivered by calling <a href="tqwidget.html#paintEvent">TQWidget::paintEvent</a>(). This virtual function is responsible for
 reacting appropriately, normally by repainting the widget. If you
 do not perform all the necessary work in your implementation of the
 virtual function, you may need to call the base class's
@@ -77,7 +77,7 @@ class's functionality, then you implement what you want and then call
 the base class.
 <p> Occasionally there isn't such an event-specific function, or the
 event-specific function isn't sufficient. The most common example is
-tab key presses. Normally, those are interpreted by <a href="ntqwidget.html">TQWidget</a> to move
+tab key presses. Normally, those are interpreted by <a href="tqwidget.html">TQWidget</a> to move
 the <a href="focus.html#keyboard-focus">keyboard focus</a>, but a few widgets need the tab key for themselves.
 <p> These objects can reimplement <a href="tqobject.html#event">TQObject::event</a>(), the general event
 handler, and either do their event handling before or after the usual
@@ -130,7 +130,7 @@ handler that was called.
 <p> postEvent() posts the event on a queue for later dispatch. The next
 time TQt's main event loop runs, it dispatches all posted events, with
 some optimization. For example, if there are several resize events,
-they are are compacted into one. The same applies to paint events: <a href="ntqwidget.html#update">TQWidget::update</a>() calls postEvent(), which minimizes flickering and
+they are are compacted into one. The same applies to paint events: <a href="tqwidget.html#update">TQWidget::update</a>() calls postEvent(), which minimizes flickering and
 increases speed by avoiding multiple repaints.
 <p> postEvent() is also often used during object initialization, since the
 posted event will typically be dispatched very soon after the