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
..
socketprocess	Remove the qmake project files	2021-01-07 15:32:28 +01:00
.gitignore	tst_qlocalsocket: get rid of QtScript dependency	2012-10-19 02:43:05 +02:00
BLACKLIST	Android: blacklist a list of failing tests for android	2020-11-04 12:27:49 +02:00
CMakeLists.txt	CMake: Regenerate projects using pro2cmake one last time	2020-12-10 11:52:30 +01:00
tst_qlocalsocket.cpp	QLocalSocket/Win: destroy the pipe before emitting final signals	2021-07-14 20:48:54 +03:00