Alex Trotsenko 6c1bc7798b QLocalSocket/Win: destroy the pipe before emitting final signals ... Both readChannelFinished() and disconnected() signals should be emitted after closing the pipe. Otherwise, these signals do not correspond to the state of the socket and may even be resent, if a slot connected to one of these signals processes events. [ChangeLog][QtNetwork][Important Behavior Changes] QLocalSocket on Windows now emits both readChannelFinished() and disconnected() signals after closing the pipe and emitting stateChanged(UnconnectedState), which is consistent with the behavior on Unix. Pick-to: 6.2 Change-Id: I1cc551b7897fdba3cec1fd6705f5396790818c7d Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>		2021-07-14 20:48:54 +03:00
..
access	QNetworkRequest: Rename (set)minimumArchiveBombSize	2021-07-02 13:05:32 +00:00
kernel	tests: fix deprecated implicit capture of this via [=]	2021-06-30 23:13:28 +02:00
selftest	Remove the qmake project files	2021-01-07 15:32:28 +01:00
socket	QLocalSocket/Win: destroy the pipe before emitting final signals	2021-07-14 20:48:54 +03:00
ssl	tst_QDtls: Move the function declaration outside the function	2021-07-02 13:05:32 +00:00
CMakeLists.txt	CMake: Regenerate subdir test projects	2020-07-09 09:38:39 +02:00