summaryrefslogtreecommitdiffstats
path: root/examples/serialport/doc/blockingreceiver.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'examples/serialport/doc/blockingreceiver.qdoc')
-rw-r--r--examples/serialport/doc/blockingreceiver.qdoc10
1 files changed, 6 insertions, 4 deletions
diff --git a/examples/serialport/doc/blockingreceiver.qdoc b/examples/serialport/doc/blockingreceiver.qdoc
index a94f7a26..71a2084d 100644
--- a/examples/serialport/doc/blockingreceiver.qdoc
+++ b/examples/serialport/doc/blockingreceiver.qdoc
@@ -4,8 +4,10 @@
/*!
\example blockingreceiver
- \title Blocking Receiver Example
+ \title Blocking Receiver
\ingroup qtserialport-examples
+ \examplecategory Connectivity
+
\brief Shows how to use the synchronous API of QSerialPort in a non-GUI thread.
\e{Blocking Receiver} shows how to create an application for a serial interface
@@ -42,8 +44,8 @@
But contrary to what many think, using threads with QThread does not
necessarily add unmanageable complexity to your application.
- This application is a Receiver, that demonstrate the work paired with Sender
- application \l{Blocking Sender Example}.
+ This application is a Receiver, that demonstrate the work paired with the
+ sender application \l{blockingsender}{Blocking Sender example}.
The Receiver application receives the request via serial port from
the Sender application and send a response to it.
@@ -137,7 +139,7 @@
\snippet blockingreceiver/receiverthread.cpp 13
- \sa {Terminal Example}, {Blocking Sender Example}
+ \sa {Serial Terminal}, {Blocking Sender}
\include examples-run.qdocinc
*/