Re: Catch WM_SIZE



"Erakis" <Erakis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E9056F9B-9215-4E8C-A55A-7A075264A8FE@xxxxxxxxxxxxxxxx
Thank for your anwser but this is not what I need.

I want to intercept this message IN my DIALOG. Not in my derived class.


The only messages you can intercept in dialog class are the ones with
_REFLECT in the name (because the message is reflected from the control,
where it goes to initially, to the parent window, the dialog). WM_SIZE is
not here. If you want the parent window to handle this, you need to
intercept WM_SIZE in your control and then do a PostMessage() of it to the
parent.

But why should the parent care when the child is sized? Usually it's the
parent who orders the child to resize in the first place.

-- David


.



Relevant Pages

  • Re: Catch WM_SIZE
    ... I want to intercept this message IN my DIALOG. ... Not in my derived class. ... where it goes to initially, to the parent window, the dialog). ... parent who orders the child to resize in the first place. ...
    (microsoft.public.vc.mfc)
  • Re: How to get the runtime class?
    ... I think it'll work in any method that the child would call inside the ... parent. ... Just probably not the ctor. ... don't define it in the derived class. ...
    (comp.lang.java.programmer)
  • Re: intercepting (setf accessor)
    ... MOP with some hacks, (SETF SLOT-VALUE-USING-CLASS) ... What i want is a way to intercept calls to (setf (parent item-instance) parent-object) ...
    (comp.lang.lisp)
  • Re: Un-ringing the bell: making parent methods unavailable to children
    ... course making the method private in the derived class will prevent it from ... > to one type of data structure as a pointer to another type via overriding ... > Addunless it is type case as its parent class. ... > polymorphism in general. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: intercepting (setf accessor)
    ... What i want is a way to intercept calls to (setf (parent item-instance) parent-object) ... Find something somewhere on:before,:after,:around, and (call-next-method) and learn those. ...
    (comp.lang.lisp)