Using a separate thread to run your socket stuff is probably a good idea in that situation.
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be ----- Original Message ----- From: "John D Algeo" <[EMAIL PROTECTED]> To: <twsocket@elists.org> Sent: Wednesday, June 04, 2008 12:48 AM Subject: [twsocket] ICS functions blocked when UI is active > I have observed that Windows does not pass messages to an application when certain User Interface functions are active. Examples are an open drop-down menu or a user dragging a window. This can cause ICS functions such as this Socket Open code to fail: > > { Use while to repeat connects to ensure enough time for reset to end } > tTarget := Time + ((FiResetTime / 1000.0) / 86400.0); > while not FfConnected and (Time < tTarget) do begin > FiLastError := SocketConnect; { Sets FfConnecting } > if FiLastError = FX_OK then > begin > { FfConnecting is cleared by FWSocketSessionConnected, may happen on > socket connection timeout } > while FfConnecting do > Application.ProcessMessages; { This can be FWSocket.MessagePump; } > end; {if FiLastError=FX_OK} > end; {while not connected} > > With a drop-down menu open, this will run as for long as FiResetTime is set (> 30 seconds) without connecting. > > Is there a way to make Windows continue to pass messages even if a drop-down menu or other UI function is active? > > Thanks, > John > -- > 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 -- 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
