----- Original Message -----
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing" <firstname.lastname@example.org>
Sent: Wednesday, February 07, 2007 3:11 PM
Subject: Re: [twsocket] Possible bug and solution in TWndControl
> Fastream Technologies wrote:
>> ----- Original Message -----
>> From: "Arno Garrels" <[EMAIL PROTECTED]>
>> To: "ICS support mailing" <email@example.com>
>> Sent: Wednesday, February 07, 2007 2:43 PM
>> Subject: Re: [twsocket] Possible bug and solution in TWndControl
>>> Fastream Technologies wrote:
>>>> I did not understand what you propose to have a single wndhandler
>>>> per thread with messages starting from WM_APP + 100--how to do it
>>> As we discussed yesterday, increase value of constant WH_MAX_MSG,
>>> the higher the value the less windows will be created but performance
>>> may decrease. An option to _force_ only one single window is not
>>> available in the component. Initialize global variable
>>> GWndHandlerMsgLow to change the base of allocated message numbers.
>> I believe you are not getting all of my messages (I cannot exactly
>> see them since I am using Gmail and Gmail blocks the messages I send
>> to mailing lists). Anyway, the WM_USER + 1 is hard coded:
> Initialize means you assign it in an Intialization section, do you?
There is no such technique in C++! I have an intermediate Pascal class but I
did not notice this technique.
> What is the purpose of creating a plain WndHandler in a worker thread?
> Please explain.
To have a never destructed handler until the thread is destructed itself!
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