The following table summarizes the breaking changes of the Ultimate UI for WPF 2017 Volume 2 Release. Detailed explanations of the issues are provided after the summary table.
- Workaround available
- No known workaround
- No known workaround, fix planned
Changed the default value of
WindowResponse from Deferred to Immediate. This means that panning and zooming actions will happen immediately as the user moves the pointer position during these actions. The previous Deferred behavior would wait until the user finished the movement before refreshing the view.
The cell UI automation peers are now virtualized. This means that you can obtain a peer only for hydrated cells, which may cause some automated tests (that rely on UI automation) to fail. If you need to switch back to the old behavior you should set the static DataPresenterBaseAutomationPeer.ProcessCellsInViewOnly property to false.
The SimpleTextBlock which is found in the editor templates found in cell templates now uses GlyphRun instead of FormattedText to display the cell text. This leads to significant performance improvements when rendering the cells but some advanced features like ligatures are not supported. If you need the old behavior you should set the inherited attached SimpleTextBlock.GlyphRunMode property to Never on either the data presenter control or any of its ancestor elements. Note that the GlyphRunMode enumeration also provides other options for selectively using GlyphRun or FormattedText based on the text being displayed.
Related topic:
Performance Optimizations Overview (xamDataPresenter)
Originally, IsSurfaceInteractionDisabled was a nullable boolean but this has been changed to a generic boolean (bool? → bool). This keeps in line with the xamPieChart’s IsSurfaceInteractionDisabled property. The property will still function the same in that if you set the property on a RingSeries it will take precedent over the one set on the xamDoughnutChart.
Starting with the release of 2017 Volume 2, the InfragisticsWPF.Controls.Charts.XamGauge assembly will no longer be available. This effectively removes the following controls:
xamLinearGauge
xamRadialGauge
xamSegmentedDisplay
The XamGeographicMap and XamMap controls used CloudMade imagery and tile sources. However, the CloudMade company made their image and tile sources unavailable. As result, we have removed support for them in the XamGeographicMap and XamMap controls.
Below is a table of the classes that were removed, the control that is affected by this change, and the assembly that contained the removed class.
We moved some classes from the InfragisticsWPF.Controls.Maps.XamGeographicMap assembly in order to support new scatter series in the XamDataChart control and provide loading of shapefile in the XamShapeChart control. The following table lists all classes that were moved:
The control now renders by default only the columns in view. Columns outside of the view are rendered once they come into view (for example when scrolling horizontally). If have control over this behavior using the MinimumNumberOfColumnsRendered property. By default its value is 0 which means that only the columns in view will be rendered, however you can set a value indicating how many columns you want to be pre-measured instead of virtualized. Please note that setting this property to higher values may lead to decreased performance results.
Fixed misspelling in AlignLabel event handler. The old name was AlignRadialGaugeLabelHangler and the new name is AlignRadialGaugeLabelHandler.