summaryrefslogtreecommitdiff
path: root/doc/src/examples
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/examples')
-rw-r--r--doc/src/examples/fingerpaint.qdoc6
-rw-r--r--doc/src/examples/orientation.qdoc2
-rw-r--r--doc/src/examples/webftpclient.qdoc4
3 files changed, 8 insertions, 4 deletions
diff --git a/doc/src/examples/fingerpaint.qdoc b/doc/src/examples/fingerpaint.qdoc
index eaef4ebd6d..7f4d77c1f1 100644
--- a/doc/src/examples/fingerpaint.qdoc
+++ b/doc/src/examples/fingerpaint.qdoc
@@ -29,8 +29,12 @@
\example touch/fingerpaint
\title Finger Paint Example
- The Finger Paint example shows the use of touch with a custom widget
+ The Finger Paint example shows the use of a touchscreen with a custom widget
to create a simple painting application.
\image touch-fingerpaint-example.png
+
+ This example was specifically designed to work with a touchscreen, using
+ QTouchEvent instead of QMouseEvent to handle user input over the custom
+ widget. As a result, it is not possible to draw with the mouse cursor.
*/
diff --git a/doc/src/examples/orientation.qdoc b/doc/src/examples/orientation.qdoc
index 8b84229470..cfe17576e7 100644
--- a/doc/src/examples/orientation.qdoc
+++ b/doc/src/examples/orientation.qdoc
@@ -130,7 +130,7 @@
Synchronizing both UIs like this might become unfeasible when there are
many things that can change. In that case it is better to make use of the
- \l{An Introduction to Model/View Programming}{Model-View-Controller pattern}
+ \l{Introduction to Model/View Programming}{Model-View-Controller pattern}
more extensively and share the content between both portrait and landscape
widgets. Then an interface for displaying and manipulating it can be tailor
made for both orientations.
diff --git a/doc/src/examples/webftpclient.qdoc b/doc/src/examples/webftpclient.qdoc
index 156dedd609..469b64590e 100644
--- a/doc/src/examples/webftpclient.qdoc
+++ b/doc/src/examples/webftpclient.qdoc
@@ -144,8 +144,8 @@
implementation provided by QFtp to perform the low level work.
In the \c FtpReply class, we need to reimplement four functions in the
- QIODevice API to ensure that it will work correctly. These functions,
- \l{QIODevice::}{abort()}, \l{QIODevice::}{bytesAvailable()},
+ API to ensure that it will work correctly. These functions,
+ \l{QNetworkReply::}{abort()}, \l{QIODevice::}{bytesAvailable()},
\l{QIODevice::}{isSequential()}, \l{QIODevice::}{readData()},
rely on the rest of the implementation to fill a QByteArray with data and
use an integer offset to track how much has been read from the device by