diff options
Diffstat (limited to 'doc/html/eventsandfilters.html')
| -rw-r--r-- | doc/html/eventsandfilters.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/html/eventsandfilters.html b/doc/html/eventsandfilters.html index b4e0729e1..668e11fe1 100644 --- a/doc/html/eventsandfilters.html +++ b/doc/html/eventsandfilters.html @@ -34,8 +34,8 @@ body { background: #ffffff; color: black; } <p> In TQt, an event is an object that inherits <a href="ntqevent.html">TQEvent</a>. Events are -delivered to objects that inherit <a href="ntqobject.html">TQObject</a> through calling <a href="ntqobject.html#event">TQObject::event</a>(). Event delivery means that an event has occurred, the -<a href="ntqevent.html">TQEvent</a> indicates precisely what, and the <a href="ntqobject.html">TQObject</a> needs to respond. Most +delivered to objects that inherit <a href="tqobject.html">TQObject</a> through calling <a href="tqobject.html#event">TQObject::event</a>(). Event delivery means that an event has occurred, the +<a href="ntqevent.html">TQEvent</a> indicates precisely what, and the <a href="tqobject.html">TQObject</a> needs to respond. Most events are specific to <a href="ntqwidget.html">TQWidget</a> and its subclasses, but there are important events that aren't related to graphics, for example, socket activation, which is the event used by <a href="ntqsocketnotifier.html">TQSocketNotifier</a> for its @@ -79,7 +79,7 @@ the base class. event-specific function isn't sufficient. The most common example is tab key presses. Normally, those are interpreted by <a href="ntqwidget.html">TQWidget</a> to move the <a href="focus.html#keyboard-focus">keyboard focus</a>, but a few widgets need the tab key for themselves. -<p> These objects can reimplement <a href="ntqobject.html#event">TQObject::event</a>(), the general event +<p> These objects can reimplement <a href="tqobject.html#event">TQObject::event</a>(), the general event handler, and either do their event handling before or after the usual handling, or replace it completely. A very unusual widget that both interprets tab and has an application-specific custom event might @@ -103,11 +103,11 @@ contain: </pre> <p> More commonly, an object needs to look at another's events. TQt -supports this using <a href="ntqobject.html#installEventFilter">TQObject::installEventFilter</a>() (and the +supports this using <a href="tqobject.html#installEventFilter">TQObject::installEventFilter</a>() (and the corresponding remove). For example, dialogs commonly want to filter key presses for some widgets, e.g. to modify Return-key handling. <p> An event filter gets to process events before the target object does. -The filter's <a href="ntqobject.html#eventFilter">TQObject::eventFilter</a>() implementation is called, and +The filter's <a href="tqobject.html#eventFilter">TQObject::eventFilter</a>() implementation is called, and can accept or reject the filter, and allow or deny further processing of the event. If all the event filters allow further processing of an event, the event is sent to the target object itself. If one of them |