Re: [twsocket] Possible bug and solution in TWndControl

2007-02-06 Thread Fastream Technologies
Ok. Then there is a bug in ThreadAttach/Detach which Arno said he did not test against. Because my code is so simple! It just has three custom messages in WM_USER + 100-103 and the ICS messages are in WM_APP + 100. The only possibility is that my init code in the client thread is bad (see the f

Re: [twsocket] Possible bug and solution in TWndControl

2007-02-06 Thread Wilfried Mestdagh
Hi, > It is just a simple constant, why shouldn't it be 800 instead of 100?? Because it is not the source of a bug. No need to change anything if it is not buggy. Changing it and then your code works does not prove there is a bug. --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/

Re: [twsocket] Possible bug and solution in TWndControl

2007-02-06 Thread Francois PIETTE
> I think Francois knows why he choosed 100 as the limit. This is completely arbitrary. Too much messages means less performance. Too less messages means too much windows. There is a tradeoff each one could adjust to his needs. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/s

Re: [twsocket] Possible bug and solution in TWndControl

2007-02-06 Thread Francois PIETTE
> BTW, where is Francois?? I'm here but working on a big contract. Sorry but free support is given after everything else is done. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: "Fastream

Re: [twsocket] Possible bug and solution in TWndControl

2007-02-06 Thread Arno Garrels
Fastream Technologies wrote: > Hello Arno, > > I am not sure I understand how could more window handles in a single > thread > would benefit than single window handle! There is for instance a bigger static array [0..WH_MAX_MSG] of TIcsWndControl.. I would play with the value and find an optimal

Re: [twsocket] Possible bug and solution in TWndControl

2007-02-06 Thread Fastream Technologies
Hello Arno, I am not sure I understand how could more window handles in a single thread would benefit than single window handle! BTW, where is Francois?? Best Regards, SZ - Original Message - From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Tuesday, February 0

Re: [twsocket] Possible bug and solution in TWndControl

2007-02-06 Thread Arno Garrels
Fastream Technologies wrote: > Despite all have been said, I still think that 100 messages/thread is > low. > It should be at least 400-600. WH_MAX_MSG does not specify the maximum possible number of messages in a thread but maximum messages handled by a single hidden window before a new window w

Re: [twsocket] Possible bug and solution in TWndControl

2007-02-06 Thread Fastream Technologies
Despite all have been said, I still think that 100 messages/thread is low. It should be at least 400-600. Regards, SZ - Original Message - From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Tuesday, February 06, 2007 2:39 PM Subject: Re: [twsocket] Possible bug a

Re: [twsocket] Possible bug and solution in TWndControl

2007-02-06 Thread Arno Garrels
> What about using RegisterWindowMessage to let windows give you a > value for > the windows-message not beeing in use? Messages are sent/posted either to a unique window handle or to a unique thread-ID so the message numbers must neither be unique in the application nor in the system. Commonly y

Re: [twsocket] Possible bug and solution in TWndControl

2007-02-06 Thread Bjørnar Nielsen
What about using RegisterWindowMessage to let windows give you a value for the windows-message not beeing in use? Usually this procedure is used when sending windows messages between applications. But I don't see a reason for not using this inside the application also. If we give the windows messa