This make me thinking we could define the messages using the highest number first and then going low. This would eliminate most clashes as many applications start from WM_USER and goes up. Easy change to do.
-- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] http://www.overbyte.be ----- Original Message ----- From: "Arno Garrels" <[EMAIL PROTECTED]> To: <twsocket@elists.org> Sent: Tuesday, June 20, 2006 6:31 PM Subject: [twsocket] About custom messages in V6 **** > Hello, > > I just 'fixed' a VERY strange V6 component behavior in a multi-threaded > server application that drove me nuts over the last hours >8-| > > V6 worked great, however I simply forgot that messages in the range > of WM_USER up to WM_USER + OverbyteIcsWndControl.WH_MAX_MSG > are now reserved for use with the TIcsWndHandler(s). So common, > custom messages sent to the same thread need to be defined above > that range! > > --- > 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
