Fastream Technologies wrote:
> Here is my settings: WH_MAX_MSG = 400 and
> 
> #define WM_HTTP_CLIENT_THREAD_ATTACH (WM_APP + 444)
> #define WM_HTTP_CLIENT_THREAD_DETACH (WM_APP + 445)
> 
> these are the two only messages. And still the same exception. 

With above messages there should be no collision, however
someone must post the message number assigned to
FMsg_WM_TRIGGER_EXCEPTION to either the thread where the
V6 component window is attached to or to the V6 component
window handle directly.

---
Arno Garrels [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html


> 
> Regards,
> 
> SZ
> 
> ----- Original Message -----
> From: "Arno Garrels" <[EMAIL PROTECTED]>
> To: "ICS support mailing" <twsocket@elists.org>
> Sent: Monday, August 07, 2006 10:25 AM
> Subject: Re: [twsocket] Test Exception in WSocket
> 
> 
>> Arno Garrels wrote:
>>> Fastream Technologies wrote:
>>>> I randomly get the test exception fired in my code.
>>> 
>>> Make sure your custom messages are in a range above
>>> WH_MAX_MSG!!
>> 
>> I mean custom messages posted to a thread, if you post
>> custom messages to a custom window it doesn't matter.
>> 
>> 
>> ---
>> Arno Garrels [TeamICS]
>> http://www.overbyte.be/eng/overbyte/teamics.html
>> 
>> 
>> --
>> To unsubscribe or change your settings for TWSocket mailing list
>> please goto http://www.elists.org/mailman/listinfo/twsocket
>> Visit our website at http://www.overbyte.be
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to