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 5282000c6..02261eb1d 100644 --- a/doc/object.doc +++ b/doc/object.doc @@ -99,7 +99,7 @@ milliseconds, until you explicitly call \l TQObject::killTimer() with 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 +loop. You start an event loop with \l TQApplication::exec(). When a 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 @@ -466,7 +466,7 @@ right-presses, etc. Since programs need to react in varied and complex ways, Qt's event delivery mechanisms are flexible. The documentation for -\l QApplication::notify() concisely tells the whole story, here we +\l TQApplication::notify() concisely tells the whole story, here we will explain enough for 99% of applications. The normal way for an event to be delivered is by calling a virtual @@ -532,7 +532,7 @@ stops processing, the target and any later event filters don't get to 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 +by installing an event filter on \l TQApplication. This is what \l 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. @@ -543,8 +543,8 @@ filters. Finally, many applications want to create and send their own events. Creating an event of a built-in type is very simple: create an object -of the relevant type, and then call \l QApplication::sendEvent() or \l -QApplication::postEvent(). +of the relevant type, and then call \l TQApplication::sendEvent() or \l +TQApplication::postEvent(). sendEvent() processes the event immediately - when sendEvent() returns, (the event filters and) the object have already processed the |