Rename date and time nt* related files to equivalent tq*

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

1 files changed, 9 insertions, 9 deletions

diff --git a/doc/object.doc b/doc/object.doc
index 381f96030..70b10682c 100644
--- a/doc/object.doc
+++ b/doc/object.doc
@@ -100,7 +100,7 @@ the timer id.
 
 For this mechanism to work, the application must run in an event
 loop. You start an event loop with \l QApplication::exec(). When a
-timer fires, the application sends a QTimerEvent, and the flow of
+timer fires, the application sends a TQTimerEvent, and the flow of
 control leaves the event loop until the timer event is processed. This
 implies that a timer cannot fire while your application is busy doing
 something else. In other words: the accuracy of timers depends on the
@@ -112,12 +112,12 @@ system. Windows 95/98 has 55 millisecond (18.2 times per second)
 accuracy; other systems that we have tested (UNIX X11 and Windows NT)
 can handle 1 millisecond intervals.
 
-The main API for the timer functionality is \l QTimer. That class
+The main API for the timer functionality is \l TQTimer. That class
 provides regular timers that emit a signal when the timer fires, and
 inherits \l TQObject so that it fits well into the ownership structure
 of most GUI programs. The normal way of using it is like this:
 \code
-    QTimer * counter = new QTimer( this );
+    TQTimer * counter = new TQTimer( this );
     connect( counter, TQ_SIGNAL(timeout()),
 	     this, TQ_SLOT(updateCaption()) );
     counter->start( 1000 );
@@ -128,24 +128,24 @@ this widget is deleted, the timer is deleted too. Next, its timeout
 signal is connected to the slot that will do the work, and finally
 it's started.
 
-QTimer also provides a simple one-shot timer API. \l QButton uses this
+TQTimer also provides a simple one-shot timer API. \l QButton uses this
 to show the button being pressed down and then (0.1 seconds later) be
 released when the keyboard is used to "press" a button, for example:
 
 \code
-    QTimer::singleShot( 100, this, TQ_SLOT(animateTimeout()) );
+    TQTimer::singleShot( 100, this, TQ_SLOT(animateTimeout()) );
 \endcode
 
 0.1 seconds after this line of code is executed, the same button's
 animateTimeout() slot is called.
 
 Here is an outline of a slightly longer example that combines object
-communication via signals and slots with a QTimer object. It
+communication via signals and slots with a TQTimer object. It
 demonstrates how to use timers to perform intensive calculations in a
 single-threaded application without blocking the user interface.
 
   \code
-    // The Mandelbrot class uses a QTimer to calculate the mandelbrot
+    // The Mandelbrot class uses a TQTimer to calculate the mandelbrot
     // set one scanline at a time without blocking the CPU. It
     // inherits TQObject to use signals and slots. Calling start()
     // starts the calculation. The done() signal is emitted when it
@@ -165,7 +165,7 @@ single-threaded application without blocking the user interface.
     private slots:
 	void calculate();
 	private:
-	QTimer timer;
+	TQTimer timer;
 	...
     };
 
@@ -448,7 +448,7 @@ activation, which is the event used by \l QSocketNotifier for its
 work.
 
 Some events come from the window system, e.g. \l QMouseEvent, some
-from other sources, e.g. \l QTimerEvent, and some come from the
+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.