Rename remaining ntq[m-r]* related files to equivalent tq* (except ntqmodules.h)

Signed-off-by: Michele Calgaro <[email protected]>

1 files changed, 12 insertions, 12 deletions

diff --git a/doc/object.doc b/doc/object.doc
index 2df02d368..52dedbc61 100644
--- a/doc/object.doc
+++ b/doc/object.doc
@@ -274,14 +274,14 @@ function calls are equivalent:
 Equivalent, that is, except that the first is faster, and provides
 much better diagnostics at compile time. When practical, the first is
 better. However, since you can get a list of all available properties
-for any TQObject through its \l QMetaObject, \l TQObject::setProperty()
+for any TQObject through its \l TQMetaObject, \l TQObject::setProperty()
 can give you control over classes that weren't available at compile
 time.
 
 As well as TQObject::setProperty(), there is a corresponding \l
-TQObject::property() function. \l QMetaObject::propertyNames() returns
-the names of all available properties. \l QMetaObject::property()
-returns the property data for a named property: a \l QMetaProperty
+TQObject::property() function. \l TQMetaObject::propertyNames() returns
+the names of all available properties. \l TQMetaObject::property()
+returns the property data for a named property: a \l TQMetaProperty
 object.
 
 Here's a simple example that shows the most important property
@@ -392,7 +392,7 @@ meta object, for example:
 \endcode
 
 Like other meta data, class information is accessible at runtime
-through the meta object, see \l QMetaObject::classInfo() for details.
+through the meta object, see \l TQMetaObject::classInfo() for details.
 
 \target override
 \section1 TQ_OVERRIDE
@@ -447,20 +447,20 @@ important events that aren't related to graphics, for example, socket
 activation, which is the event used by \l TQSocketNotifier for its
 work.
 
-Some events come from the window system, e.g. \l QMouseEvent, some
+Some events come from the window system, e.g. \l TQMouseEvent, some
 from other sources, e.g. \l TQTimerEvent, and some come from the
 application program. TQt is symmetric, as usual, so you can send
 events in exactly the same ways as Qt's own event loop does.
 
-Most events types have special classes, most commonly \l QResizeEvent,
-\l TQPaintEvent, \l QMouseEvent, \l TQKeyEvent and \l TQCloseEvent.
+Most events types have special classes, most commonly \l TQResizeEvent,
+\l TQPaintEvent, \l TQMouseEvent, \l TQKeyEvent and \l TQCloseEvent.
 There are many others, perhaps forty or so, but most are rather odd.
 
 Each class subclasses TQEvent and adds event-specific functions; see,
-for example, \l QResizeEvent. In the case of QResizeEvent, \l
-QResizeEvent::size() and \l QResizeEvent::oldSize() are added.
+for example, \l TQResizeEvent. In the case of TQResizeEvent, \l
+TQResizeEvent::size() and \l TQResizeEvent::oldSize() are added.
 
-Some classes support more than one event type. \l QMouseEvent
+Some classes support more than one event type. \l TQMouseEvent
 supports mouse moves, presses, shift-presses, drags, clicks,
 right-presses, etc.
 
@@ -477,7 +477,7 @@ do not perform all the necessary work in your implementation of the
 virtual function, you may need to call the base class's
 implementation; for example:
 \code
-    MyTable::contentsMouseMoveEvent( QMouseEvent *me )
+    MyTable::contentsMouseMoveEvent( TQMouseEvent *me )
     {
 	// my implementation