Community
Participate
Working Groups
PropertySheetEntry orders its properties alphabetically. This provides deterministic ordering in the case of merged properties. There are many cases however where implementor's of IPropertySource would like to control the ordering. NOTES:
PRODUCT VERSION: 136
This could be solved by allowing subclassing of PropertySheetEntry
Defer. The ordering should be consistent for the user.
This is a reoccuring issue that people want. For example if there is a bounds property with sub properties, when you expand the bounds users want to see: - bounds x y width height rather than - bounds height width x y
Reopen for investigation
*** This bug has been marked as a duplicate of 2597 ***