Hi Wilfried,
use starting from WM_USER.
You don't have to worry because you send / post messages to specific
windows, so the right window will receive it.
I know, but the problem is that the VCL can also post messages to the same
window, especially 3rd party components.
Paul
--
To
wrote:
They start at WM_USER + 1.
So there can be a conflict.
I think I better switch to WM_APP then
Paul
- Original Message -
From: Arno Garrels arno.garr...@gmx.de
To: ICS support mailing twsocket@elists.org
Sent: Sunday, May 03, 2009 9:26 PM
Subject: Re: [twsocket] OT: WM_USER
I'm using window message in range WM_USER+1 to WM_USER+200.
For a long time, I've wondering why a http-client sometimes stops working
although all messages do thru a message queue.
Now, I'm told not to use messages in the WM_USER range, but in WM_APP range
since third party components and
Paul wrote:
I'm using window message in range WM_USER+1 to WM_USER+200.
For a long time, I've wondering why a http-client sometimes stops
working although all messages do thru a message queue.
Now, I'm told not to use messages in the WM_USER range, but in WM_APP
range since third party
Arno Garrels wrote:
ID. You hopefully do not post/send common messages (not registered
by AllocateMsgHandlers) to the ICS window in V6 and better.
Sorry, when I said common, I meant custom message IDs, in the range
ICS V6 and better might allocate for own purposes (search for
They start at WM_USER + 1.
So there can be a conflict.
I think I better switch to WM_APP then
Paul
- Original Message -
From: Arno Garrels arno.garr...@gmx.de
To: ICS support mailing twsocket@elists.org
Sent: Sunday, May 03, 2009 9:26 PM
Subject: Re: [twsocket] OT: WM_USER or WM_APP
