In my test dialog I have a CTreeCtrl
and a CMFCPropertyGridCtrl
:
When I run these controls in dark mode they look like this:
The CTreeCtrl
still has the expandable icons as a square with +/-. But the CMFCPropertyGridCtrl
is now using a v
down symbol. IN other MFC applications I still have the square. I can't find a setting for this.
I saw this mentioned on a webpage but it doesn't appear to be valid (might be be the right type of control):
When you change the
TreeButtonStyle
of the property grid toTreeView
, the expand collapse image reverts to the defaultOffice2010Silver
skin style.
Side-point, if I use:
// This causes the tree control to use down arrows (but no dark mode support)
SetWindowTheme(m_treeCtrl.GetSafeHwnd(), L"Explorer", nullptr);
It causes the tree control to use the same arrow style:
Removing that line returns back to the square symbol. No I can't woprk out how to change the property grid control.
In my test dialog I have a CTreeCtrl
and a CMFCPropertyGridCtrl
:
When I run these controls in dark mode they look like this:
The CTreeCtrl
still has the expandable icons as a square with +/-. But the CMFCPropertyGridCtrl
is now using a v
down symbol. IN other MFC applications I still have the square. I can't find a setting for this.
I saw this mentioned on a webpage but it doesn't appear to be valid (might be be the right type of control):
When you change the
TreeButtonStyle
of the property grid toTreeView
, the expand collapse image reverts to the defaultOffice2010Silver
skin style.
Side-point, if I use:
// This causes the tree control to use down arrows (but no dark mode support)
SetWindowTheme(m_treeCtrl.GetSafeHwnd(), L"Explorer", nullptr);
It causes the tree control to use the same arrow style:
Removing that line returns back to the square symbol. No I can't woprk out how to change the property grid control.
Share Improve this question edited Feb 2 at 17:07 Andrew Truckle asked Feb 2 at 16:50 Andrew TruckleAndrew Truckle 19.2k17 gold badges84 silver badges218 bronze badges1 Answer
Reset to default 0This is only a partial answer because it fixes this issue, and causes another