On Tuesday, June 04, 2013 8:11 AM [GMT+1=CET], Merijn Bosma schrob: > Thanks for the quick fix Arno! > Did Francois agree with the solution found by Eric?
I don't know. But turning off winsock notification right before the call to closesocket() should be safe. The current fix additionally reenables notification messages if the call to closesocket() failed with error WSAEWOULDBLOCK before the MessagePump is called. -- Arno -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
