The following table summarizes the breaking changes of the Ultimate UI for WPF 2016 Volume 1 Release. Detailed explanations of the issues are provided after the summary table.
– Workaround available
– No known workaround
– No known workaround, fix planned
The location for the TriangulationSource class has been removed from the xamGeographicMap assembly and has been moved to the shared DataVisualization assembly.
The default value of the AllowFieldMoving property is changed from Yes to WithinLogicalRow.
Workaround:
If you want to retain the old behavior you can set AllowFieldMoving property to Yes.
You may not be able to access fields defined in XAML using the FieldLayout's Fields collection prior the initialization of the particular field layout (for example this may not be possible in the xamDataGrid’s Loaded event).
Workarounds:
You may use the FieldLayout's FieldItems collection which contains the fields definitions prior the FieldLayout is initialized. Since the FieldItems collection is using the FieldItem type you may need to up-cast to the Field type in order to access the Field specific properties.
You may use the xamDataGrid’s FieldLayoutInitialized event to get notified for the moment in time at which a specific FieldLayout gets initialized which means its Fields and FieldItems collections are populated and synchronized.
The name of the xamGeographicMap’s ShouldKeepResourcesOnUnload property has been changed.
The default visibility of the recurrence label in the xamSchedule’s recurrence dialog is now visible for German and French languages.
Workaround:
If you want to retain the old behavior you can add a string resource which configures the visibility to a resource file (.resx) and register this resource file on any of the xamSchedule’s views as described in the related topic below.