Me.numericYAxis.LabelSettings = New AxisLabelSettings() Me.numericYAxis.LabelSettings.Extent = 40
This topic lists breaking changes in the 2011 Volume 1 release of the Ultimate UI for WPF product.
The default value of LabelSettings property of an Axis is null and this property must be instantiated with the AxisLabelSettings constructor before accessing properties of axis labels.
In Visual Basic:
Me.numericYAxis.LabelSettings = New AxisLabelSettings() Me.numericYAxis.LabelSettings.Extent = 40
In C#:
this.numericYAxis.LabelSettings = new AxisLabelSettings(); this.numericYAxis.LabelSettings.Extent = 40;
Names of resource dictioneries for the Office 2010 Blue theme has been changed:
Office2010Blue.xamZoombar.xaml -> Office2010Blue.DataVisualization.xaml
Dynamic Layout Changes
Some application scenarios involve dynamic addition or removal of node items from the graph. This behavior is supported when the data model implements INotifyPropertyChanged. However, please note that any changes to the underlying node data will cause the xamNetworkNode to update its layout, modifying the positions of existing nodes. In future, the control will provide a mechanism for preserving the locations of existing nodes when nodes are added or removed.
Node Overlap
In some cases, the layout algorithm for the Network Node control may cause nodes to overlap. This will be addressed as development continues.
When working with xamQRCodeBarcode™ control, be sure to include the following assembly to your project:
InfragisticsWPF.Encodings.v11.1.dll
The encodings were extracted in a separate assembly to reduce the size of the InfragisticsWPF.Controls.Barcodes.v11.1 assembly. The xamQRCodeBarcode control is the only barcode symbology from the xamBarcode™ series of controls, which uses encodings that are not supported by the WPF framework.
Note that Infragistics Barcode Reader™ requires reference to the InfragisticsWPF.Encodings.v11.1 assembly to decode QR Code symbols.
Starting from the 2011 Volume 1 release, the FlatDataSource requires unique names for hierarchies on which to base the slice of data to be computed for the xamPivotGrid control instead of specifying only the dimension name because there was just one hierarchy per dimension in prior releases.
In C#:
// In the 2011 Volume 1 release:
xmlaDataSource.Rows = DataSourceBase.GenerateInitialItems("[Date].[Calendar], [Region].[Country]");
xmlaDataSource.Columns = DataSourceBase.GenerateInitialItems("[Company].[Product]");
// In the 2010 Volume 3 release:
xmlaDataSource.Rows = DataSourceBase.GenerateInitialItems("[Date], [Region]");
xmlaDataSource.Columns = DataSourceBase.GenerateInitialItems("[Company]");
This change affects the developers that have implemented their custom data provider for the xamPivotGrid control. The following methods of the DataProviderBase class have changed:
In C#:
protected void OnLoadMeasureGroupsCompleted(AsyncCompletedEventArgs)protected void OnLoadMeasureGroupDimensionsCompleted(AsyncCompletedEventArgs)These methods now need to be called with the cube as third parameter in the constructor of the AsyncCompletedEventArgs object.
In C#:
this.OnLoadMeasureGroupsCompleted(new AsyncCompletedEventArgs(e.Error, e.Cancelled, cube)); this.OnLoadMeasureGroupDimensionsCompleted(new AsyncCompletedEventArgs(e.Error, e.Cancelled, cube));
Another change which concerns the custom data providers in conjunction with the proper work of pre-filtering feature is the need to implement the LoadMembersAsync(ICube cube, IHierarchy hierarchy) method. When there are pre-filters applied the whole hierarchy must be populated. That happens through a call to the LoadMembersAsync method. When all members of the hierarchy are filled into the hierarchy this method call should be as follows in order to fire the related event and notify the data source that operation is completed:
In C#:
this.OnLoadMembersCompleted(new AsyncCompletedEventArgs(e.Error, e.Cancelled, hierarchy));