diff options
Diffstat (limited to 'doc/html/eventsandfilters.html')
| -rw-r--r-- | doc/html/eventsandfilters.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/html/eventsandfilters.html b/doc/html/eventsandfilters.html index f8ec0e46e..44ff1c3b1 100644 --- a/doc/html/eventsandfilters.html +++ b/doc/html/eventsandfilters.html @@ -53,7 +53,7 @@ supports mouse moves, presses, shift-presses, drags, clicks, right-presses, etc. <p> Since programs need to react in varied and complex ways, TQt's event delivery mechanisms are flexible. The documentation for -<a href="ntqapplication.html#notify">TQApplication::notify</a>() concisely tells the whole story, here we +<a href="tqapplication.html#notify">TQApplication::notify</a>() concisely tells the whole story, here we will explain enough for 99% of applications. <p> The normal way for an event to be delivered is by calling a virtual function. For example, <a href="tqpaintevent.html">TQPaintEvent</a> is delivered by calling <a href="tqwidget.html#paintEvent">TQWidget::paintEvent</a>(). This virtual function is responsible for @@ -113,14 +113,14 @@ event, the event is sent to the target object itself. If one of them stops processing, the target and any later event filters don't get to see the event at all. <p> It's also possible to filter <em>all</em> events for the entire application, -by installing an event filter on <a href="ntqapplication.html">TQApplication</a>. This is what <a href="tqtooltip.html">TQToolTip</a> does in order to see <em>all</em> the mouse and keyboard activity. +by installing an event filter on <a href="tqapplication.html">TQApplication</a>. This is what <a href="tqtooltip.html">TQToolTip</a> does in order to see <em>all</em> 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. <p> The global event filters are called before the object-specific filters. <p> Finally, many applications want to create and send their own events. <p> Creating an event of a built-in type is very simple: create an object -of the relevant type, and then call <a href="ntqapplication.html#sendEvent">TQApplication::sendEvent</a>() or <a href="ntqapplication.html#postEvent">TQApplication::postEvent</a>(). +of the relevant type, and then call <a href="tqapplication.html#sendEvent">TQApplication::sendEvent</a>() or <a href="tqapplication.html#postEvent">TQApplication::postEvent</a>(). <p> sendEvent() processes the event immediately - when sendEvent() returns, (the event filters and) the object have already processed the event. For many event classes there is a function called isAccepted() |