Pascal Chapon wrote:
> Okay, everything is fine if I do it with a PostMessage and process
> the non-blocking loop in a separate procedure.
Yes, that is the solution.
Not to call the message pump in event handlers is one of the
Ten Coding Commandments, not just in ICS.
--
Arno
--
To unsubsc
thout this last call to app.ProcessMessages, I'll keep you up (not at the
company yet...).
Is the only "theoritically proper" solution to handle this kind of mandatory
discussion with a separate thread?
Pascal
>Objet : Re: [twsocket] Problem with DataAvailable (similar)
>Pa
f mandatory
discussion with a separate thread?
Pascal
>Objet : Re: [twsocket] Problem with DataAvailable (similar)
>Pascal Chapon wrote:
>> Any idea?
>Do you call the message pump directly or indirectly, for instance,
>Application.ProcessMessages or ShowMessage() in one of the ICS
Pascal Chapon wrote:
> Any idea?
Do you call the message pump directly or indirectly,
for instance, Application.ProcessMessages or ShowMessage()
in one of the ICS event handlers?
--
Arno
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi
Hi,
I've found this message in the Feb 2013 archives, and as I experience a similar
problem (although in LineMode), I gave a try to the wsoNoReceiveLoop option.
Unfortunately, the problem still persists.
I must add that, just before being stuck exactly like Robert below, so on the
very previou
Robert Dorn wrote:
> Hello
>
> (sorry, my english is not soo good ;) )
>
> I have a client and a server program and i use binary mode. The
> communication between the both programs
> works great. But after a few time one of the programs no longer call
> the OnDataAvailable event. But still sendin
Hello
(sorry, my english is not soo good ;) )
I have a client and a server program and i use binary mode. The
communication between the both programs
works great. But after a few time one of the programs no longer call the
OnDataAvailable event. But still sending on both programs. the progr
