Understanding a paragraph from an article

[zspirit]

I am reading this article http://www.microsoft.com/msj/0699/c/c0699.aspx
and come across the follwing: (please search a small string to find it).

If you start from scratch, you create your window by calling CWnd::Create or some overloaded version, such as CView::Create or CButton::Create. Or—as in the case of views—MFC calls Create for you. In all these cases, control eventually arrives at CWnd::CreateEx.

It is confusing to me. Does the authors means even if call CButton::Create(), eventually CWnd::CreateEx() will be called a result? But I thought it is overloaded so the base class doesn't get called!?

Does the base calls CWnd::Create() or CWnd::CreateEx() get called if I created a button or list which have its own Create() or CreateEx() function?

[GCDEF]

An overridden or overloaded function in a derived class can still call the base class implementation of that function.

[zspirit]

An overridden or overloaded function in a derived class can still call the base class implementation of that function.

Right which usually is the case with message handlers but many times we override a function for sole reason not to call the base class function so to modify it. Irrespectively I think in the case of Create() function, it doesn't add up if we Create window in say CButton class and than call a base class to Create the same window again!?

[John E]

but many times we override a function for sole reason not to call the base class function so to modify it.

That's true in some cases but not true in all cases. Sometimes you override a base class function for the purpose of adding some functionality. In other words, doing whatever the base class does, then doing something extra that's needed in the derived class but isn't needed in the base class. There are no hard and fast rules (except for constructors).

To be honest it doesn't matter whether a button's Create() function calls CWnd's Create() function or not. All that matters is that the button's Create() function will create a valid button. If it needs to call Create() in the base class it will do so - but that shouldn't be of any consequence as far as your use of CButton is concerned. It isn't something you need to worry about.

[zspirit]

To be honest it doesn't matter whether a button's Create() function calls CWnd's Create() function or not. All that matters is that the button's Create() function will create a valid button. If it needs to call Create() in the base class it will do so - but that shouldn't be of any consequence as far as your use of CButton is concerned. It isn't something you need to worry about.

I am creating a light weight GUI library which wrap up win32 style APIs so wanted to look at how it works. But the code inside CButton explains it. Thanks.

BOOL CButton::Create(LPCTSTR lpszCaption, DWORD dwStyle,
        const RECT& rect, CWnd* pParentWnd, UINT nID)
{
    CWnd* pWnd = this;
    return pWnd->Create(_T("BUTTON"), lpszCaption, dwStyle, rect, pParentWnd, nID);
}