The enhanced grid view feature uses a single root-level panel instead of multiple nested panels to arrange all RecordPresenter objects. If you upgrade your application from a previous version of the Ultimate UI for WPF product, this change will be applied automatically to the xamDataGrid™and xamDataPresenter™ controls in your application resulting in the following issues:
Any animations or triggers in the RecordPresenter object’s template dealing with nested records will be ignored.
Nested records will not be surrounded by chrome.
Application logic that assumes a nested element structure may fail.
Bindings that assume a nested element structure may fail.
Logic that uses UIAutomation to access information may be impacted. The automation objects are still returned as a nested tree but the tree is not guaranteed to be identical to the tree returned when using nested elements.
If the changes affect your application, you can work around the changes in two different ways. Either you can modify your application logic/bindings or you can set the GridViewSettings object’s UseNestedPanels property to True. For more information on the enhanced grid view, read About Hierarchical Records and Performance.
If you created a FieldLayout object without setting its Key property, the DataPresenter controls automatically assign a default key to your field layout. The default key that the DataPresenter controls assign to the FieldLayout object has changed. This change will not affect your application if you already assigned keys to your FieldLayout objects in a previous version.
The following table lists the changes based on the data source.
If the changes affect your application, you can either set the FieldLayout object’s Key property explicitly or modify your application logic to use the new keys.
The DataPresenter controls have a new default group-by area (GroupByAreaMulti) that allows your end users to drag a field’s headers directly from the record area to the group-by area and vice-versa. In addition, the new group-by area displays instances of LabelPresenter objects. Therefore, the LabelPresenter object’s styling and functionality in the new group-by area will be consistent with the DataPresenter control’s LabelPresenter objects. This change will affect your application in the following manner:
Any application logic or style that modifies the previous group-by area or group-by area field labels will be ignored.
The GroupByArea and GroupByAreaFieldLabelStyle properties will be ignored unless the GroupByAreaMode property is set to DefaultFieldLayoutOnly.
If a DataPresenter control’s view does not display field headers (LabelPresenter objects), your end users will not be able to use the new group-by area. This will usually only be an issue with the xamDataCarousel™ control since it does not display field headers by default.
Any bindings inside a LabelPresenter object’s style that assumes it is inside a RecordPresenter object or a HeaderLabelArea object will fail.
If the change affects your application, you can modify your application logic to use the DataPresenter control’s GroupByAreaMulti property or you can revert to the previous group-by area by setting the DataPresenter control’s GroupByAreaMode to DefaultFieldLayoutOnly. In addition, your styles should target the new GroupByAreaMulti control and you can use the LabelPresenter object’s IsInGroupByArea and IsInFieldChooser properties in triggers.