[solved] CXTPTabClientWnd::OnMDIDestroy bug?

Is this an oversight/bug?

In CXTPTabClientWnd::OnMDIDestroy, the method always calls either ActivateNextItem or ActivateNextTopmostItem. So what happens if I have, for example, three documents opened and I hit the "x" on the tab of a window that is not the active MDI window?

CodeJock deactivates the active window and activates another window depending on the tab order. This seems wrong since clicking the "x" on an inactive window does not MDI activate that window (which happens to be one of the big benefits in our system to using MDI tabs).

To see this open three documents. We are using "new tabs on the left flag". Activate the doc that goes with the right-most tab. Now hit the "x" on the middle tab. The document associated with the left-most tab activates and the active document deactivates. Since the document being closed was not active, why pick another document to activate?

I "fixed" this by getting the active window and seeing if it is the one being closed. Only if it is do I activate another document.

...

    CWnd* pActive = MDIGetActive();

    bool bClosingActive = false;

    if( pActive )
    {
        if( pActive->GetSafeHwnd() == (HWND)wParam )
        {
            bClosingActive = true;
        }
    }
    if( bClosingActive )
    {
        if (m_afterCloseTabPosition == xtpWorkspaceActivateNextToClosed)
            ActivateNextItem(FindItem((HWND)wParam));
        else if (m_afterCloseTabPosition == xtpWorkspaceActivateTopmost)
        //    ActivateNextTopmostItem(FindItem((HWND)wParam));
    }

...