Doc: Fix typo and mismatch between code and description
Fixes: QTBUG-107675 Pick-to: 6.4 6.2 Change-Id: I38140617a2b0525db417137aa41a52a389b3bea3 Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
This commit is contained in:
parent
ef1c1132e6
commit
de7287be69
@ -123,7 +123,7 @@
|
||||
The final part of our loop is that we acquire the mutex so that we can
|
||||
safely read from our member data. We then let the thread go to sleep by
|
||||
calling QWaitCondition::wait(). At this point, we can go back to
|
||||
requestNewFortune() and look closed at the call to wakeOne():
|
||||
requestNewFortune() and look closely at the call to wakeOne():
|
||||
|
||||
\snippet blockingfortuneclient/fortunethread.cpp 1
|
||||
\dots
|
||||
|
@ -48,7 +48,7 @@
|
||||
to the connecting socket. This is a common way to transfer binary data
|
||||
using QTcpSocket. First we create a QByteArray and a QDataStream object,
|
||||
passing the bytearray to QDataStream's constructor. We then explicitly set
|
||||
the protocol version of QDataStream to QDataStream::Qt_4_0 to ensure that
|
||||
the protocol version of QDataStream to QDataStream::Qt_5_10 to ensure that
|
||||
we can communicate with clients from future versions of Qt (see
|
||||
QDataStream::setVersion()). We continue by streaming in a random fortune.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user