Re: [twsocket] ICS functions blocked when UI is active

2008-06-04 Thread Francois Piette
://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

Re: [twsocket] ICS functions blocked when UI is active

2008-06-04 Thread Dod
Hello, I personnaly always create and manage the socket component in a separated thread. This permit to avoid such problem, and also when the reverse appear when your socket procedures has a very high activity that could slow down the main's app message queue that make it less

Re: [twsocket] ICS functions blocked when UI is active

2008-06-04 Thread Wilfried Mestdagh
Hello John, Normally this is no problem. I think with dropdown menu open there is no problem also, because windows is pumping messages when a menu is open. But depending on your applicaiton you can do the socket thing in a separate thread. Other possibility is to run the communication in a NT

[twsocket] ICS functions blocked when UI is active

2008-06-03 Thread John D Algeo
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