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.
SelectedPropertyDefinitions are not cleared when RadPropertyGrid.Item being changed.
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.
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.
Expose an event corresponding to AutogeneratingPropertyDefinition so that the user can customize the property definitions.