summaryrefslogtreecommitdiffstats
path: root/doc/signalsandslots.doc
diff options
context:
space:
mode:
authorMichele Calgaro <michele.calgaro@yahoo.it>2024-09-04 11:53:23 +0900
committerMichele Calgaro <michele.calgaro@yahoo.it>2024-09-04 13:56:43 +0900
commit0582c90a9ed4b965629267713f51c0da7c38b39d (patch)
treecae95e850081d0a7f2be6cef5837f43a28d53d2c /doc/signalsandslots.doc
parent39f8a475b4ec5c87a11a7e9300a30ef1c5b4a7e1 (diff)
downloadtqt-0582c90a.tar.gz
tqt-0582c90a.zip
Rename remaining ntq[m-r]* related files to equivalent tq* (except ntqmodules.h)
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/signalsandslots.doc')
-rw-r--r--doc/signalsandslots.doc4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/signalsandslots.doc b/doc/signalsandslots.doc
index 65dfa9dfa..e58e199b5 100644
--- a/doc/signalsandslots.doc
+++ b/doc/signalsandslots.doc
@@ -240,8 +240,8 @@ return types (i.e. use \c void).
A note about arguments. Our experience shows that signals and slots
are more reusable if they do \e not use special types. If \l
TQScrollBar::valueChanged() were to use a special type such as the
-hypothetical \c QRangeControl::Range, it could only be connected to
-slots designed specifically for QRangeControl. Something as simple as
+hypothetical \c TQRangeControl::Range, it could only be connected to
+slots designed specifically for TQRangeControl. Something as simple as
the program in \link tutorial1-05.html Tutorial #1 part 5\endlink
would be impossible.