Currently, the order of the GroupDefinitions will be based on the OrderIndex of the PropertyDefinitions, which means that in order to reorder the groups, you will have to order the PropertyDefinitions.

The GroupDefinition class exposes the DisplayIndex property, which we can review and improve its functionality to allow the user to directly order the groups based on it.

Add a property on the PropertyDefinition or the PropertyGridField object that changes the visibility of the expand/collapse button that is displayed when you have nested properties. The developer should be able to manually define if the button should be visible or not.

See if we can improve the TryGetValueByReflection method when using dynamic objects.

Add the ability to add new items in the collection editor when binding to primitive types.

Add a Visibility DependencyProperty (to support data binding) to the GroupDefinition class. The same setting is available in the PropertyDefinition objects and it affects the property fields in the UI. The Visibility of the GroupDefinitions should hide/show the entire group along with all its child property fields.

The GroupDefinition Visibility should not update the Visibility of the child PropertyDefinition objects. Both properties should work independent.

A memory leak occurs when RadPropertyGrid instaces are loaded/unloaded multiple times. 

The issue manifests even more if the PropertyGrid contains fields for editing DateType types. 

 Add selected inactive state for PropertyGrid Field.

Add an event that is raised when the editor's value gets updated and just before the value is updated back to the associated data item when PropertySetMode is Union or Intersection.

Currently, you can use the PropertySetsValidationFunction to intercept this moment, but the function is not invoked only for the currently edited property, but for all other properties in the PropertyGrid and you cannot indicate which one triggered the change.

Improve loading performance when IsGrouped="True" and AutoExpandGroups="True".

Currently the AutomationID of the PropertyGridField is set to "{0}_FieldEditor", where {0} is the DisplayName of the property definition. We can introduce an option to prevent this.

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.

 

 SelectedPropertyDefinitions are not cleared when RadPropertyGrid.Item being changed.

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.

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.