Hello Paul, 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.
WM_USER = 0x400 WM_APP = 0x8000 Windows help say: Message numbers in the second range (WM_USER through 0x7FFF) can be defined and used by an application to send messages within a private window class. Message numbers in the third range (0x8000 through 0xBFFF) are reserved for future use by Windows. --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz Sunday, May 3, 2009, 21:46, Paul 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" <[email protected]> > To: "ICS support mailing" <[email protected]> > Sent: Sunday, May 03, 2009 9:26 PM > Subject: Re: [twsocket] OT: WM_USER or WM_APP >> 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 >> GWndHandlerMsgLow in OverbyteIcsWndControl.pas, there are comments). >> It's no problem to post/send Windows messages such as WM_QUIT etc.. >> >> -- >> Arno Garrels >> >> >> -- >> To unsubscribe or change your settings for TWSocket mailing list >> please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket >> Visit our website at http://www.overbyte.be >> -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
