diff options
author | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-07-24 21:06:28 +0900 |
---|---|---|
committer | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-07-28 18:25:42 +0900 |
commit | 8ef4ea451dd81dd66b34ed31aaa631f6df24a192 (patch) | |
tree | fb639fd5c35cb99f87172bc61484f5bf74b6beb9 /doc/html/eventsandfilters.html | |
parent | 0e787fb7f5b56b4fe87cd8ada64ae740bbca87bc (diff) | |
download | tqt3-8ef4ea451dd81dd66b34ed31aaa631f6df24a192.tar.gz tqt3-8ef4ea451dd81dd66b34ed31aaa631f6df24a192.zip |
Rename environment class nt* related files to equivalent tq*
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/html/eventsandfilters.html')
-rw-r--r-- | doc/html/eventsandfilters.html | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/html/eventsandfilters.html b/doc/html/eventsandfilters.html index caea373ab..890229bd5 100644 --- a/doc/html/eventsandfilters.html +++ b/doc/html/eventsandfilters.html @@ -33,9 +33,9 @@ body { background: #ffffff; color: black; } -<p> In TQt, an event is an object that inherits <a href="ntqevent.html">TQEvent</a>. Events are +<p> In TQt, an event is an object that inherits <a href="tqevent.html">TQEvent</a>. Events are 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 +<a href="tqevent.html">TQEvent</a> indicates precisely what, and the <a href="tqobject.html">TQObject</a> needs to respond. Most events are specific to <a href="tqwidget.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="tqsocketnotifier.html">TQSocketNotifier</a> for its @@ -47,7 +47,7 @@ events in exactly the same ways as TQt's own event loop does. <p> Most events types have special classes, most commonly <a href="qresizeevent.html">TQResizeEvent</a>, <a href="tqpaintevent.html">TQPaintEvent</a>, <a href="qmouseevent.html">TQMouseEvent</a>, <a href="qkeyevent.html">TQKeyEvent</a> and <a href="qcloseevent.html">TQCloseEvent</a>. There are many others, perhaps forty or so, but most are rather odd. -<p> Each class subclasses <a href="ntqevent.html">TQEvent</a> and adds event-specific functions; see, +<p> Each class subclasses <a href="tqevent.html">TQEvent</a> and adds event-specific functions; see, for example, <a href="qresizeevent.html">TQResizeEvent</a>. In the case of <a href="qresizeevent.html">TQResizeEvent</a>, <a href="qresizeevent.html#size">TQResizeEvent::size</a>() and <a href="qresizeevent.html#oldSize">TQResizeEvent::oldSize</a>() are added. <p> Some classes support more than one event type. <a href="qmouseevent.html">TQMouseEvent</a> supports mouse moves, presses, shift-presses, drags, clicks, @@ -85,15 +85,15 @@ handling, or replace it completely. A very unusual widget that both interprets tab and has an application-specific custom event might contain: <p> <pre> - bool MyClass:event( <a href="ntqevent.html">TQEvent</a> *evt ) { - if ( evt-><a href="ntqevent.html#type">type</a>() == TQEvent::KeyPress ) { + bool MyClass:event( <a href="tqevent.html">TQEvent</a> *evt ) { + if ( evt-><a href="tqevent.html#type">type</a>() == TQEvent::KeyPress ) { <a href="qkeyevent.html">TQKeyEvent</a> *ke = (TQKeyEvent *)evt; if ( ke-><a href="qkeyevent.html#key">key</a>() == Key_Tab ) { // special tab handling here ke-><a href="qkeyevent.html#accept">accept</a>(); return TRUE; } - } else if ( evt-><a href="ntqevent.html#type">type</a>() >= TQEvent::User ) { + } else if ( evt-><a href="tqevent.html#type">type</a>() >= TQEvent::User ) { <a href="qcustomevent.html">TQCustomEvent</a> *ce = (TQCustomEvent*) evt; // custom event handling here return TRUE; @@ -136,7 +136,7 @@ increases speed by avoiding multiple repaints. posted event will typically be dispatched very soon after the initialization of the object is complete. <p> To create events of a custom type, you need to define an event number, -which must be greater than <a href="ntqevent.html#Type-enum">TQEvent::User</a>, and probably you also need +which must be greater than <a href="tqevent.html#Type-enum">TQEvent::User</a>, and probably you also need to subclass <a href="qcustomevent.html">TQCustomEvent</a> in order to pass characteristics about your custom event. See the documentation to <a href="qcustomevent.html">TQCustomEvent</a> for details. |