6c45b1817f
Due to the bug related to the 'new syntax' signal/slot connections, it's unfortunately possible to have a connection not deleted properly by the moment children objects get deleted. Then, as a result, in e.g. QSslSocket's destructor the socket will change its state, triggering the (now deleted) UI elements' access. Note - the original bug was reported, the patch (only possible?) was not accepted. Fixes: QTBUG-83659 Change-Id: I2965532485bcd46f93f8449e4d0a30da92b572c5 Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io> |
||
|---|---|---|
| .. | ||
| blockingfortuneclient | ||
| broadcastreceiver | ||
| broadcastsender | ||
| dnslookup | ||
| doc | ||
| download | ||
| downloadmanager | ||
| fortuneclient | ||
| fortuneserver | ||
| googlesuggest | ||
| http | ||
| loopback | ||
| multicastreceiver | ||
| multicastsender | ||
| multistreamclient | ||
| multistreamserver | ||
| network-chat | ||
| securesocketclient | ||
| secureudpclient | ||
| secureudpserver | ||
| shared | ||
| threadedfortuneserver | ||
| torrent | ||
| network.pro | ||
| README | ||
Qt is provided with an extensive set of network classes to support both client-based and server side network programming. These examples demonstrate the fundamental aspects of network programming with Qt. Documentation for these examples can be found via the Examples link in the main Qt documentation.