Add documentation about reconnect attempts.
Task-number: QTBUG-18082 Change-Id: I3cf667bcd9929d1fc3e8d3c5f9d4e612dddd181e Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
This commit is contained in:
parent
b0b754632e
commit
49af23e776
@ -208,6 +208,10 @@
|
|||||||
This signal is emitted after an error occurred. The \a socketError
|
This signal is emitted after an error occurred. The \a socketError
|
||||||
parameter describes the type of error that occurred.
|
parameter describes the type of error that occurred.
|
||||||
|
|
||||||
|
When this signal is emitted, the socket may not be ready for a reconnect
|
||||||
|
attempt. In that case, attempts to reconnect should be done from the event
|
||||||
|
loop. For example, use a QTimer::singleShot() with 0 as the timeout.
|
||||||
|
|
||||||
QAbstractSocket::SocketError is not a registered metatype, so for queued
|
QAbstractSocket::SocketError is not a registered metatype, so for queued
|
||||||
connections, you will have to register it with Q_DECLARE_METATYPE() and
|
connections, you will have to register it with Q_DECLARE_METATYPE() and
|
||||||
qRegisterMetaType().
|
qRegisterMetaType().
|
||||||
|
Loading…
x
Reference in New Issue
Block a user