summaryrefslogtreecommitdiffstats
path: root/doc/object.doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/object.doc')
-rw-r--r--doc/object.doc14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/object.doc b/doc/object.doc
index af9162f7e..f434930c6 100644
--- a/doc/object.doc
+++ b/doc/object.doc
@@ -438,10 +438,10 @@ buttons.
\title Events and Event Filters
-In Qt, an event is an object that inherits \l QEvent. Events are
+In Qt, an event is an object that inherits \l TQEvent. Events are
delivered to objects that inherit \l TQObject through calling \l
TQObject::event(). Event delivery means that an event has occurred, the
-QEvent indicates precisely what, and the TQObject needs to respond. Most
+TQEvent indicates precisely what, and the TQObject needs to respond. Most
events are specific to \l TQWidget and its subclasses, but there are
important events that aren't related to graphics, for example, socket
activation, which is the event used by \l TQSocketNotifier for its
@@ -456,7 +456,7 @@ Most events types have special classes, most commonly \l QResizeEvent,
\l TQPaintEvent, \l QMouseEvent, \l QKeyEvent and \l QCloseEvent.
There are many others, perhaps forty or so, but most are rather odd.
-Each class subclasses QEvent and adds event-specific functions; see,
+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.
@@ -501,15 +501,15 @@ interprets tab and has an application-specific custom event might
contain:
\code
- bool MyClass:event( QEvent *evt ) {
- if ( evt->type() == QEvent::KeyPress ) {
+ bool MyClass:event( TQEvent *evt ) {
+ if ( evt->type() == TQEvent::KeyPress ) {
QKeyEvent *ke = (QKeyEvent *)evt;
if ( ke->key() == Key_Tab ) {
// special tab handling here
ke->accept();
return TRUE;
}
- } else if ( evt->type() >= QEvent::User ) {
+ } else if ( evt->type() >= TQEvent::User ) {
QCustomEvent *ce = (QCustomEvent*) evt;
// custom event handling here
return TRUE;
@@ -564,7 +564,7 @@ posted event will typically be dispatched very soon after the
initialization of the object is complete.
To create events of a custom type, you need to define an event number,
-which must be greater than \c QEvent::User, and probably you also need
+which must be greater than \c TQEvent::User, and probably you also need
to subclass \l QCustomEvent in order to pass characteristics about
your custom event. See the documentation to \l QCustomEvent for
details.