An non edit mode is enabled in the control when the EditMode is set to Single. In this case, only one field can enter edit mode and the rest are read only.
Currently, there is no API that allows you to customize the content (that shows the property value) of the read only fields.
Add an API that allows you to customize the read only content. Similar to the EditorTemplate of the PropertyDefinition.
Currently, the control allows you to search only for fields that have been expanded already. If a parent field was never expanded, the search won't look for its children.
Allow searching in not expanded fields.
Behind the scene we need to update any changes made in the property grid, in a SQL Server database, too. With our current implementation we fire a database request if a property is edited in the property grid. This is fine if only one entity has been selected. If more than one entity has been selected (ProperytSetMode “Intersection”) a database request is fired for each entity if a property is edited. This is not very performant for us. We need an event like “EditEnded” to figure out when the PropertySetViewModel has updated all ViewModels. Then we are able to updated the necessary changes in the database in a single call.
By the time being, a custom DataTemplate can be applied only for the EditorTemplate. When the EditMode is Single, a plain TextBlock is used for a readonly PropertyDefinition. With the Default EditMode, if the EditorTemplate is set, it will be displayed, but the user needs to stick to the default behavior provided by the ReadOnlyEditorState property (grayed out and disabled element for its Disabled value, and enabled interaction for the ReadOnly one). Provide an option to directly set a ReadOnlyTemplate for both EditModes.
Currently the only option is to call the Expand/Collapse groups API, which takes noticable time to execute.
Currently, when RenderMode Flat is enabled, RadPropertyGridd uses a custom navigation behavior. The default framework navigation is available only when RenderMode is Hierarchical.
Add an additional EditorAttribute's constructor which takes the type's name as a string.
Available in the 2017 R1 Release (2017.1.117).
Expose a boolean property that states whether to save the expanded state of the group and property definitions and the filter descriptor.
Currently, if you change the value of a property in the object bound to the property grid control, the control's UI won't reflect this change.
I understand from http://docs.telerik.com/devtools/wpf/controls/radpropertygrid/features/validation, that there are essentially two methods to implement data validation in a RadPropertyGrid. Note that I would like to use the "property set" feature of RadPropertyGrid whereby I can display/edit properties from multiple items simultaneously (http://docs.telerik.com/devtools/wpf/controls/radpropertygrid/features/defining-propertysets). I was only able to get the second validation technique (data annotations) to work when using property sets. Should the first technique (IDataErrorInfo) work with the property sets feature? Towards the end of the discussion here http://www.telerik.com/forums/validation-bfd78b274562, this topic is touched on, but it is not clear if it was ever resolved. If it is not possible to use the IDataErrorInfo technique with property sets, I suggest the documentation at http://docs.telerik.com/devtools/wpf/controls/radpropertygrid/features/validation be updated to reflect this fact. Separately, is there a target date for when this feature may be added? If it is possible to use the IDataErrorInfo technique with property sets, would someone kindly post a sample solution?