This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
The new ExpandedMode property on the WPF PropertyGrid works great. However, not all Themes display the initially expanded nodes correctly. Several of the Themes work correctly: OfficeBlue, Radium, and Whalesong as well as no Theme at all. For them, the expand icon on the left side of the node indicates the node is expanded and in fact it is. For the others -- Alloy, AlloyLight, OfficeBlack and OfficeSilver -- the expand icon appears as if the node is expanded, but the node is actually collapsed. If you click on the icon, the expanded node briefly appears and then quickly collapses and the icon (correctly) now shows the node as collapsed. If you click on the icon again, it switches to show the node as expanded and the node does expand. I attached a sample program (PGTheme) to illustrate the issue. When you click on one of the dogs in the list of dogs to show, it's properties are displayed in the PropertyGrid below the list. The property for the dog's offspring is a collection of other dogs that should be expanded by default. You can add additional offspring by clicking the '+' button on the right side of the Offspring node. Those dogs should also appear expanded. To see the problem, uncomment one of the Themes in the ResourceDictionary.MergedDictionary at the top of the DefaultTheme.xaml file, rebuild, run the program, and select one of the dogs in the list. Note the state of the expander icon on the left side of the Offspring node and the expanded state of the collection. I'd like to use the Alloy theme, but it's not handling the expanded mode correctly. Any suggestions? BillBR |
|
|
Hello BillBR Thanks for pointing out this anomaly. This will be resolved in all themes in the next nightly build. Jason Fauchelle |
|
|
The fix works great now for all Themes! Thanks, BillBR |
|