Thank you for your feedback! You have rated this topic in the last 30 days.
Breaking Changes in 2014 Volume 1
Breaking Changes Summary
Breaking changes summary chart
The following table summarizes the breaking changes of the Ultimate UI for WPF 2014 Volume 1 Release. Detailed explanations of the issues and the existing workarounds are provided after the summary table.
In order to enhance the implementation of the custom item filtering in the control, the following properties were changed: ItemsFilter and CustomItemsFilter.
Change in the SelectionChanged event argument type
The type of the event argument of the SelectionChanged event is changed from EventArgs to SelectionChangedEventArgs in order to provide information for selected/unselected control’s items.
To work around this breaking change rename all occurrences of the old event’s argument type with the new one.
Changes in item filtering implementation and renamed properties
In order to enhance the custom item filtering in the control, the following properties were changed:
ItemsFilter
CustomItemsFilter
Till the 2014 Volume 1 release, only one filter was possible to apply in the control. After creating an ItemsFilter object, it was set to the XamComboEditor/ XamMultiColumnComboEditorCustomItemsFilter property.
When creating a custom ComboItemFilter, the ComboItemFilterFieldName property must be set to the name of the data property to be filtered. If FieldName property is not set, an exception is thrown.
Following is a table that lists the old properties names and the new ones:
Old Property Name
New Property Name
Infragistics.Controls.Editors.ItemsFilter
Infragistics.Controls.Editors.ComboItemFilter
Infragistics.Controls.Editors.CustomItemsFilter
Infragistics.Controls.Editors.ItemFilters
For more information about implementing custom item filtering, check the following topics: