Professional UI Solutions
Site Map   /  Register
 
 

Forum

Please Log In to post a new message or reply to an existing one. If you are not registered, please register.

NOTE: Some forums may be read-only if you are not currently subscribed to our technical support services.

Forums » Prof-UIS Tech Support » Windows messages Collapse All
Subject Author Date
Seth Strong Jan 22, 2007 - 11:24 AM

Does prof-uis use special windows messages? We ran into trouble with WM_USER + 6 and I don’t know where the problem came from but if you have reserved messages I would like to know.

Thanks,
Seth

Seth Strong Jan 25, 2007 - 12:32 PM

That’s backwards from what I meant. Something else seems to be intercepting the WM_USER+6 message that I send and crashes my application. It’s my fault for broadcasting the message but I don’t know what class is really messing up.

Technical Support Jan 29, 2007 - 9:14 AM

We would not recommend you using WM_USER messages because there is always a possibility that someone else is also using a message with the very same ID. So it it is possible to avoid using WM_USER, you could use the RegisterWindowMessage() function to retrieve a unique message ID.



Seth Strong Jan 23, 2007 - 7:47 AM

I use SendMessageToDescendants() to reflect messages as appropriate to my application. When I reflected the message defined as WM_USER + 6, my slider control glitched and changed its number of tic marks and became unresponsive. When I redefined the message as WM_USER + 608, everything works fine. I tried to isolate the behavior and I think it is due to the broadcasting of WM_USER + 6 to all decendants but I don’t know why.

Technical Support Jan 23, 2007 - 11:20 AM

You can find out what is sending the unwanted (WM_USER+6) message simply by setting up breakpoints in message handlers for this message. The call stack window should show you where it is sent from.

Technical Support Jan 22, 2007 - 11:51 AM

We do not use (WM_USER+6) message in Prof-UIS. The WM_USER message is used in the resizable property sheet/page components only. Please let us know more about the problem.