[fix] stop worker thread properly on TuioClient disconnect (win only)

[Ivan-Grebennikov]

I think there is one major disadvantage of TuioClient::disconnect().
It's not synchronous. So after it returns there is no guarantee that client has disconnected.
This can lead in undesirable consequences. For example, take a look at this snippet:

std::unique_ptr<TUIO::TuioClient> tuioClient = std::make_unique<TUIO::TuioClient>();
tuioClient->connect();
/// later...
tuioClient->disconnect();
tuioClient.reset()

This snippet can lead to segfault or zombie working thread because of TuioClient destructor call and internal structures cleanup while the working thread is still running.

This PR makes TuioClient::disconnect() synchronous. The main idea is that we use

TUIO11_CPP/oscpack/ip/win32/UdpSocket.cpp

Line 499 in 7d5dd6d

void AsynchronousBreak()

to stop the thread. It raises _breakEvent in

TUIO11_CPP/oscpack/ip/win32/UdpSocket.cpp

Line 502 in 7d5dd6d

SetEvent( breakEvent_ );

which in turn helps us to force immediate break from the working thread polling loop:

TUIO11_CPP/oscpack/ip/win32/UdpSocket.cpp

Line 448 in 7d5dd6d

DWORD waitResult = WaitForMultipleObjects( (DWORD)socketListeners_.size() + 1, &events[0], FALSE, waitTime );

and after we wait for thread finish using WaitForSingleObject().

Using just

TUIO11_CPP/oscpack/ip/win32/UdpSocket.cpp

Line 494 in 7d5dd6d

void Break()

leads to wait forever for new data on sockets and just break after, but what if we deinitialize network in other non-worker thread? (to be concrete ~TuioClient() calls

TUIO11_CPP/oscpack/ip/win32/NetworkingUtils.cpp

Line 74 in 7d5dd6d

WSACleanup();

in the chain of destructors and this leads to zombie thread that will never return from

TUIO11_CPP/oscpack/ip/win32/UdpSocket.cpp

Line 448 in 7d5dd6d

DWORD waitResult = WaitForMultipleObjects( (DWORD)socketListeners_.size() + 1, &events[0], FALSE, waitTime );

).

This edit is just for Win because I have no opportunity to test it on Unix...

Feel free to comment.
Ivan