Add an additional EditorAttribute's constructor which takes the type's name as a string.

Hello,
my question is about RadPropertyGrid.
The case if following. I use objects implementing ICustomTypeDescriptor, call it ClassTypeDescriptor, as items source for property grid and properties are derived from PropertyDescriptor class. It is important to have these objects grouped and sorted. That's why I pass System.ComponentModel.DataAnnotations.DisplayAttribute with GroupName and Order values set to the constructor of PropertyDescriptor. If I bind Item property of property grid direct to ClassTypeDescriptor, everything works like a charm, properties get grouped and sorted. But if I bind Item property to the List or any other collection of ClassTypeDescriptor, independently from the count of elements in it, grouping is getting lost and sorting is not applied also. I attach the demo solution to this report and hope for the quick answer.

P.S.: I've tried the same case but with "normal" object with properties. And grouping and sorting work even if I bind a collection to Item property of PropertyGrid

Thank you in advance
Alexander Sherekin

Currently, when RenderMode Flat is enabled, RadPropertyGridd uses a custom navigation behavior. The default framework navigation is available only when RenderMode is Hierarchical.

Currently the only option is to call the Expand/Collapse groups API, which takes noticable time to execute.

The Exception is thrown as if the RenderMode is not set to Flat. If the GroupStyleSelector is defined before the RenderMode, the issue is not reproduced.

If an EditorAttribute's EditorStyle is set to None and a custom usercontrol is used as an editor, the DataContext of the usercontrol is not respected.


Available in LIB version 2017.1.417 , it will be also available in the R2 2017 Release. 

Modify the current implementation so that the TypeConverter is applied as well when its GetStandardValues method is not overriden.

Available in LIB version 2017.1.417 , it will be also available in the R2 2017 Release. 

Available in LIB version 2017.3.1127, it will be also available in the R1 2018 Release.

The item status is set to Declined as it is already logged in our system: https://feedback.telerik.com/Project/143/Feedback/Details/202982-propertygrid-selectedpropertydefinitions-are-not-cleared-when-radpropertygrid-it.

When a RadPropertyGrid instance is placed inside a RadBusyIndicator, the StyleManager cannot apply the styles correctly and it causes an InvalidOperationException at runtime.

Workaround: Use the NoXaml version of the assemblies with the needed themes.