diff options
| author | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-08-25 15:36:25 +0900 |
|---|---|---|
| committer | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-08-29 22:23:36 +0900 |
| commit | 0917fbb5387978eb7b2e2fd68bcb6beaa8c46505 (patch) | |
| tree | 0ef68a6a92087957855c7607ac176821d10d049d /doc/object.doc | |
| parent | 7b1d2ad2df8cd011b487c43336aa67639fa359c9 (diff) | |
| download | tqt-0917fbb5.tar.gz tqt-0917fbb5.zip | |
Rename remaining ntq[a-c]* related files to equivalent tq* (except ntqapplication.h and ntqconfig.h)
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/object.doc')
| -rw-r--r-- | doc/object.doc | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/object.doc b/doc/object.doc index ec18c7216..027d8371c 100644 --- a/doc/object.doc +++ b/doc/object.doc @@ -453,7 +453,7 @@ 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 QKeyEvent and \l QCloseEvent. +\l TQPaintEvent, \l QMouseEvent, \l QKeyEvent 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, @@ -510,7 +510,7 @@ contain: return TRUE; } } else if ( evt->type() >= TQEvent::User ) { - QCustomEvent *ce = (QCustomEvent*) evt; + TQCustomEvent *ce = (TQCustomEvent*) evt; // custom event handling here return TRUE; } @@ -565,8 +565,8 @@ 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 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 +to subclass \l TQCustomEvent in order to pass characteristics about +your custom event. See the documentation to \l TQCustomEvent for details. */ @@ -581,7 +581,7 @@ details. When you create a TQObject with another object as parent, it's added to the parent's \link TQObject::children() children() \endlink list, and is deleted when the parent is. It turns out that this approach fits -the needs of GUI objects very well. For example, a \l QAccel (keyboard +the needs of GUI objects very well. For example, a \l TQAccel (keyboard accelerator) is a child of the relevant window, so when the user closes that window, the accelerator is deleted too. |