summaryrefslogtreecommitdiffstats
path: root/doc/html/eventsandfilters.html
diff options
context:
space:
mode:
authorMichele Calgaro <michele.calgaro@yahoo.it>2024-07-15 19:08:22 +0900
committerMichele Calgaro <michele.calgaro@yahoo.it>2024-07-18 09:31:41 +0900
commita30f5359f03c3017fa19a6770fab32d25d22cb87 (patch)
treecb365dd7a1c3666e3f972c6cad04be7b8e846cba /doc/html/eventsandfilters.html
parent25ad1267da6916e738a126ff5a9b41cd686adfc6 (diff)
downloadtqt-a30f5359.tar.gz
tqt-a30f5359.zip
Rename graphics class nt* related files to equivalent tq* (part 1)
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/html/eventsandfilters.html')
-rw-r--r--doc/html/eventsandfilters.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/html/eventsandfilters.html b/doc/html/eventsandfilters.html
index 2f40d036d..caea373ab 100644
--- a/doc/html/eventsandfilters.html
+++ b/doc/html/eventsandfilters.html
@@ -45,7 +45,7 @@ from other sources, e.g. <a href="tqtimerevent.html">TQTimerEvent</a>, and some
application program. TQt is symmetric, as usual, so you can send
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="qpaintevent.html">TQPaintEvent</a>, <a href="qmouseevent.html">TQMouseEvent</a>, <a href="qkeyevent.html">TQKeyEvent</a> and <a href="qcloseevent.html">TQCloseEvent</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,
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.
@@ -57,7 +57,7 @@ event delivery mechanisms are flexible. The documentation for
<a href="ntqapplication.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="qpaintevent.html">TQPaintEvent</a> is delivered by calling <a href="tqwidget.html#paintEvent">TQWidget::paintEvent</a>(). This virtual function is responsible for
+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
reacting appropriately, normally by repainting the widget. If you
do not perform all the necessary work in your implementation of the
virtual function, you may need to call the base class's