Defining a custom *constructor* (not initializer!)

[Steven Schveighoffer]

On Fri, 11 May 2012 10:04:00 -0400, Mehrdad <wfunction at hotmail.com> wrote:

>> I'm probably not getting the entire picture here, but I assume from  
>> your description that CreateWindow directly calls your WndProc.  If  
>> that is the case, isn't it guaranteed that after the base ctor runs the  
>> class has received the WM_CREATE message?  I mean, the only issue  
>> happens when you are not quite through the ctor chain, no?
>
> Right, what I'm saying is that it's the *subclass* who needs the  
> notification more, than anyone else (although, for other reasons, the  
> base class needs it as well).
> The whole point is to get the messages to the *subclasses* properly...

Yeah, but given that the subclass is calling the base constructor, and the  
base constructor does not return until WM_CREATE is received, can't the  
subclass constructor pretend it received the message?

-Steve