v17 (final) Forgot Theme on CXTPTreeCtrl

And CXTPListView.

It's relatively simple to configure yourself. I use the old hack:

ON_WM_SYSCOLORCHANGE()

// in cpp where you set the theme. I use mainframe since it's global:

SendMessageToDescendants(WM_SYSCOLORCHANGE, 0, 0L, TRUE, FALSE);

// When you change a theme, the message is posted to descendants of the mainframe. Each module can respond to the message with something similar to that illustrated below:

// in header
afx_msg void OnSysColorChange();

// in cpp
BEGIN_MESSAGE_MAP
     ON_WM_SYSCOLORCHANGE()

// make a handler using the theme value from wherever you set themes from. Again, mine is stored in mainframe.

void CMyReportView::OnSysColorChange()
{
    GetReportCtrl().SetTheme(((CMainFrame*)AfxGetMainWnd())->GetReportTheme());
    GetReportCtrl().RedrawControl();
}

Unless you use WM_SYSCOLORCHANGE for anything else, you should be good to go.

Unfortunately, there is no "one theme fits all" integrated method for all controls. It becomes problematic if you want some things to use a common theme and other things you don't - perhaps it requires something like a "theme override" byte for each control? That's how I'd do it 

The current CJ method offers more flexibility but makes it more difficult to create a single pattern for changing themes.

Hello cpede -

Sorry, perhaps I didn't understand your question. I don't know if v. 17 has the same capability as the v. 16.26 I'm using, but it has been possible to theme the header of a CXTPListCtrl for some time. As shown:

// xtpControlThemeResource is an XTPControlTheme enum. Any of the enums should work.

bool MyListCtrl::Init()
{
    CXTPListCtrl::Init();
    HWND hWndHeader = GetDlgItem(0)->GetSafeHwnd();
    m_header.SubclassWindow(hWndHeader);
    m_header.EnablePopupMenus(TRUE);
    m_header.SetTheme(xtpControlThemeResource);
    return true;
}

I agree the developer should be able to choose when and where to apply themes/skins.