Re: Custom Control - Notifcation Messages
Hi Scott,
Thanks for the quick response.
Your absolutely right about the Send/Post.
I just started messing around making my own notification messages.
I'm just curious as to how Notification messages actually work.
I am a bit confused about WM_PARENTNOTIFY and WM_NOTIFY.
I think I am on the right track. I just need verification.
Thanks,
"Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp> wrote in message =
news:ctSdnXtPWvICqSjbnZ2dnUVZ_vumnZ2d@comcast.com...
Nobody wrote:
Hi,
I just started messing around with creating my own custom control =
notification messages,
so I am just curious about the inner workings of notifcation =
messages.
This is more or less just the philosphy behind notification messages =
and how they work.
Here, I have created my own notification message.
struct MOUSE
{
HWND hwndFrom;
UINT idFrom;
UINT code;
UINT nFlags;
CPoint point;
};
In the class, I extantiate the object
class CSomeControl
{
private:
MOUSE Mouse;
}
Then, in OnLButtonDown, OnLButtonUp, OnMouseMove, I send a =
Notifcation message.
if(GetMouseEvents()) //If MouseEvents Notifcation Messages Enabled
{
Mouse.hwndFrom = GetSafeHwnd();
Mouse.idFrom = ID_MYCONTROL;
Mouse.code = UWM_MYCONTROL_LBUTTONDOWN;
Mouse.nFlags = nFlags;
Mouse.point = point;
GetParent()->PostMessage(WM_NOTIFY, UWM_MYCONTROL_LBUTTONDOWN, =
(LPARAM)&Mouse);
}
Is that basically how it is done?
No, this has a bad bug. PostMessage returns to you before the message =
is processed. Then OnMouseMove might occur before the message is
processed, so you PostMessage again but you have now wiped out the
previous data in the Mouse struct, even though the handler of the =
first
message has not seen it yet. Solution: You must use SendMessage =
instead
of PostMessage. SendMessage does not return until the message has =
been
processed.
--
Scott McPhillips [MVP VC++]