summaryrefslogtreecommitdiffstats
path: root/doc/kommander/tutorials.docbook
diff options
context:
space:
mode:
authorMichele Calgaro <michele.calgaro@yahoo.it>2023-09-25 13:59:20 +0900
committerMichele Calgaro <michele.calgaro@yahoo.it>2023-09-26 10:27:28 +0900
commit74d7a64994b02e7d880f4e9960f653b2510d48d8 (patch)
tree24cc990fbaa09028b97544fc8c9da64f9bb549fb /doc/kommander/tutorials.docbook
parent5df35638d9979618b39681efcda8bd05d7c96cf8 (diff)
downloadtdewebdev-4b645e7e11b9e054a48744dfcf99bf0fc0a2cb0a.tar.gz
tdewebdev-4b645e7e11b9e054a48744dfcf99bf0fc0a2cb0a.zip
Replace QObject, QWidget, QImage, QPair, QRgb, QColor, QChar, QString, QIODevice with TQ* versionr14.1.1
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it> (cherry picked from commit 0580616e20b68c764cdbbd9a01c9dd21f99766d4)
Diffstat (limited to 'doc/kommander/tutorials.docbook')
-rw-r--r--doc/kommander/tutorials.docbook2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/kommander/tutorials.docbook b/doc/kommander/tutorials.docbook
index 6071c60c..a9ccafa8 100644
--- a/doc/kommander/tutorials.docbook
+++ b/doc/kommander/tutorials.docbook
@@ -83,7 +83,7 @@ One of the very useful features inherited from Qt Designer was signals and slots
<para>
To access the connection tool you can open it by right clicking anywhere on the dialog and selecting it. Click the menu and you will see a list of connections made at the bottom. Above that are two lists of signals and slots and above them the respective sender and receiver are selected. An easy way to make connections is visually. Look at the toolbar or the Tools menu. There are three items grouped there. A pointer, signals and slot connections and the tab order or widgets. Selecting this sets connection mode for the curios. Click on your widget to send the signal and drag it to your widget to receive it in a slot. As you do this you will see a line and drop indications on the widget under the mouse. The StatusBar on the Editor will tell you what is being connected.
</para>
-<note><para>In version 1.3 there is a &kommander; function connect() which allows you to connect signals and slots on the fly. This is useful if you just used createWidget. Obviously you can't use the dialog for something &kommander; doesn't yet know exists. Unfortunately there are too many combinations to list so you have to type out signals and slots. <emphasis>These must be typed verbatim or they will fail.</emphasis> This is where the connection tool is handy again. Open it and select two widgets like the two you want to connect and read the connection information. if it says <command>execute(const QString&amp;)</command> that is exactly what you must type.</para></note>
+<note><para>In version 1.3 there is a &kommander; function connect() which allows you to connect signals and slots on the fly. This is useful if you just used createWidget. Obviously you can't use the dialog for something &kommander; doesn't yet know exists. Unfortunately there are too many combinations to list so you have to type out signals and slots. <emphasis>These must be typed verbatim or they will fail.</emphasis> This is where the connection tool is handy again. Open it and select two widgets like the two you want to connect and read the connection information. if it says <command>execute(const TQString&amp;)</command> that is exactly what you must type.</para></note>
</sect2>
<sect2 id="slot-functions">