运行时创建Tree ComboBox控件触发断言问题求助

I’ve dealt with similar MFC custom control creation headaches before, so let’s walk through resolving your runtime assertion error, plus confirm the necessary TRACE statement tweak you noted.

First: Apply the Required TRACE Fix #

First off, make sure you’ve updated the line in ComboTreeCtrlExt.cpp as you mentioned:

Replace TRACE1(_T("Item selected: %s\n"), GetItemText(hItem)); with TRACE(_T("Item selected: %s\n"), GetItemText(hItem));

This fixes a mismatch in the TRACE macro parameters that could cause silent issues or crashes in debug builds.

Troubleshooting the Runtime Creation Assertion #

The assertion firing in dbgrptt.cpp at _CrtDbgBreak() usually points to a problem with control initialization, window class registration, or invalid parameters during CreateEx. Here’s how to fix it:

1. Fix Window Class Registration Timing #

Putting RegisterWindowClass() in the constructor is risky because the control object hasn’t been associated with a HWND yet, and you might be trying to register the class before MFC’s internal setup is complete. Instead:

• Move the class registration to run right before you call CreateEx, or override PreSubclassWindow() to handle it (if you’re subclassing an existing control).
• Add error checking to ensure the class registers successfully. Update your RegisterWindowClass() method like this:

BOOL CTreeComboBox::RegisterWindowClass()
{
    WNDCLASS wc;
    // Check if the class is already registered to avoid duplicates
    if (::GetClassInfo(AfxGetInstanceHandle(), _T("TreeComboBox"), &wc))
        return TRUE;

    wc.style = CS_HREDRAW | CS_VREDRAW;
    wc.lpfnWndProc = ::DefWindowProc;
    wc.cbClsExtra = 0;
    wc.cbWndExtra = sizeof(LONG_PTR);
    wc.hInstance = AfxGetInstanceHandle();
    wc.hIcon = NULL;
    wc.hCursor = AfxGetApp()->LoadStandardCursor(IDC_ARROW);
    wc.hbrBackground = (HBRUSH)(COLOR_WINDOW + 1);
    wc.lpszMenuName = NULL;
    wc.lpszClassName = _T("TreeComboBox");

    if (!AfxRegisterClass(&wc))
    {
        AfxMessageBox(_T("Failed to register TreeComboBox window class!"));
        return FALSE;
    }
    return TRUE;
}

Then call this method explicitly before CreateEx in your dialog code:

void CTestComboBoxDlg::OnBnClickedButton1()
{
    // Ensure the class is registered first
    if (m_ComboBox2.RegisterWindowClass())
    {
        m_ComboBox2.CreateEx(WS_EX_CLIENTEDGE, 
                            _T("TreeComboBox"), 
                            _T(""), 
                            WS_CHILD | WS_VISIBLE | CBS_DROPDOWN, 
                            CRect(100, 100, 300, 400), 
                            this, 
                            IDC_CUSTOM_TREECOMBO);
    }
}

2. Verify CreateEx Parameters #

Double-check these critical parameters—invalid values here are a common source of assertions:

• Window Class Name: Must match exactly what you registered (_T("TreeComboBox")), not the default COMBOBOX class.
• Control Styles: Include WS_CHILD | WS_VISIBLE plus either CBS_DROPDOWN or CBS_DROPDOWNLIST (the Tree ComboBox relies on these combo box base styles).
• Parent Window: Ensure this (your dialog) is a valid, initialized window (which it will be in OnInitDialog or button click events).

3. Check Control Object Lifetime #

Make sure m_ComboBox2 is a member variable of your dialog class, not a local variable inside OnInitDialog or the button click handler. Local variables get destroyed when the function exits, leaving invalid HWND references that trigger assertions.

4. Debug the Exact Assertion #

When the assertion fires, look up the call stack in Visual Studio to find the actual assertion line in MFC or the control code (not just _CrtDbgBreak()). For example:

• If it’s an assertion about a null HWND, your CreateEx call is failing (check return value!).
• If it’s about GDI objects, verify m_BrushAlert is initialized correctly and only used after the control is created, and that it’s not selected into a DC when DeleteObject() is called in the destructor.

Test the Fix #

After making these changes, rebuild your project:

1. First test creating the control in OnInitDialog to confirm basic functionality.
2. Then test the button-click dynamic creation scenario.

If the assertion is gone and the Tree ComboBox works as expected, you’re good to go!

内容的提问来源于stack exchange，提问作者vg8open