aboutsummaryrefslogtreecommitdiffstats
path: root/src/qml/doc/src/javascript/expressions.qdoc
diff options
context:
space:
mode:
authorSze Howe Koh <szehowe.koh@gmail.com>2014-03-16 12:20:26 +0800
committerThe Qt Project <gerrit-noreply@qt-project.org>2014-03-18 13:17:42 +0100
commit5a9b5148a1d3fb412ab9bae276c10ba1a44374b1 (patch)
tree99ec4b4e32e4fbd0e9d10705f5c38a1fd56a223b /src/qml/doc/src/javascript/expressions.qdoc
parent303db2e8a19ea1f2c1b8d5dc59e2754b0d03bd61 (diff)
Doc: Fix broken \qmlsignal links
Fix the breaks caused by the re-categorizing of \qmlsignal pages Task-number: QTBUG-35846 Change-Id: I528ae16ec522fc902133e22d8f53c87a7f0d56ad Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Diffstat (limited to 'src/qml/doc/src/javascript/expressions.qdoc')
-rw-r--r--src/qml/doc/src/javascript/expressions.qdoc10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/qml/doc/src/javascript/expressions.qdoc b/src/qml/doc/src/javascript/expressions.qdoc
index 13238b2e43..02ca20cd28 100644
--- a/src/qml/doc/src/javascript/expressions.qdoc
+++ b/src/qml/doc/src/javascript/expressions.qdoc
@@ -143,11 +143,11 @@ Those signals can be handled by signal handler functions, which can be defined
by clients to implement custom program logic.
Suppose that a button represented by a Rectangle type has a MouseArea and a
-Text label. The MouseArea will emit its "pressed" signal when the user presses
-the defined interactive area, which will automatically trigger the
-\l{MouseArea::}{onPressed} handler, which can be defined by clients. The QML
-engine will execute the JavaScript expressions defined in the onPressed and
-onReleased handlers, as required. Typically, a signal handler is bound to
+Text label. The MouseArea will emit its \l{MouseArea::}{pressed} signal when the
+user presses the defined interactive area, which will automatically trigger the
+\c onPressed handler, which can be defined by clients. The QML
+engine will execute the JavaScript expressions defined in the \c onPressed and
+\c onReleased handlers, as required. Typically, a signal handler is bound to
JavaScript expressions to initiate other events or to simply assign property
values.