diff options
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 70b10682c..a5c3b13fb 100644 --- a/doc/object.doc +++ b/doc/object.doc @@ -415,14 +415,14 @@ achieve this using the following code: TQ_OVERRIDE( bool autoMask DESIGNABLE true SCRIPTABLE true ) \endcode -Another example is QToolButton. By default QToolButton has a read-only +Another example is TQToolButton. By default TQToolButton has a read-only "toggleButton" property, because that's what it inherits from QButton: \code TQ_PROPERTY( bool toggleButton READ isToggleButton ) \endcode But we want to make our tool buttons able to be toggled, so we write a -WRITE function in QToolButton, and use the following property override +WRITE function in TQToolButton, and use the following property override to make it acessible: \code TQ_OVERRIDE( bool toggleButton WRITE setToggleButton ) @@ -533,7 +533,7 @@ see the event at all. It's also possible to filter \e all events for the entire application, by installing an event filter on \l QApplication. This is what \l -QToolTip does in order to see \e all the mouse and keyboard activity. +TQToolTip does in order to see \e all the mouse and keyboard activity. This is very powerful, but it also slows down event delivery of every single event in the entire application, so it's best avoided. @@ -599,8 +599,8 @@ box. You can also delete child objects yourself, and they will remove themselves from their parents. For example, when the user removes a -toolbar it may lead to the application deleting one of its \l QToolBar -objects, in which case the tool bar's \l QMainWindow parent would +toolbar it may lead to the application deleting one of its \l TQToolBar +objects, in which case the tool bar's \l TQMainWindow parent would detect the change and reconfigure its screen space accordingly. The debugging functions \l TQObject::dumpObjectTree() and \l |