This topic provides information on the currently known issues and limitations related to the Ultimate UI for WPF product. We will be working to address the known issues in future releases of the product.
This section contains a list of the issues in the current release of the product that will be addressed in future hot fixes and/or full releases.
If you install the samples, and then compile the source code, when you attempt to uninstall the samples, the files that were complied will still remain. This is due to the fact that the installer only keeps track of what it creates. So since you compiled the samples, the installer will not delete those files. You will have to manually delete those files and folders yourself.
The documentation for Ultimate UI for WPF 2010.1 cannot be installed at the same time with other documentation versions. For example, it is not possible to have the product documentation for Ultimate UI for WPF 2010.1 installed along with the product documentation for Ultimate UI for WPF 2010.2 on the same computer. The documentation for Ultimate UI for WPF 2010.1 should be uninstalled before installing newer versions. There is no such limitations regarding the documentation versions 2010.2 and higher.
The ExportOptions object’s ExcludeExpandState property only affects root-level records.
When you add a theme assembly to your project in Microsoft® Expression® Blend, its Copy Local property is automatically set to True. In this case, the CLR will not load the theme assembly at run time. The side effect of this behavior is that the external theme will not be applied to the controls in your application even if you set the control’s Theme property to the name of the external theme. For example, if you add the InfragisticsWPF.Themes.Fall.dll theme assembly to your project in Expression Blend and set the xamDataGrid™ control’s Theme property to "Fall", the fall theme will not be applied to the xamDataGrid control at run time. You must either reference a type in the fall theme assembly or set the theme assembly’s Copy Local property to False. For cases where you need to set the theme assemblies' Copy Local property to True, you can use the following example code to load the assembly.
In XAML:
<!--The XAML will load the theme assembly and apply the theme to all DataPresenters in your Window even if you do not set their Theme properties.-->
<Window.Resources>
<ResourceDictionary>
<ResourceDictionary.MergedDictionaries>
<igThemeFall:DataPresenter
xmlns:igThemeFall="http://infragistics.com/Themes/Fall" />
</ResourceDictionary.MergedDictionaries>
</ResourceDictionary>
</Window.Resources>In Visual Basic:
'TODO: Put this code in the application's Application.xaml.vb file.
Protected Overrides Sub OnStartup(ByVal e As StartupEventArgs)
MyBase.OnStartup(e);
'You do not have to access any of the class' members.
'The CLR will load the assembly when you instantiate a class from the theme assembly.
Dim temp As New Infragistics.Windows.Themes.Fall.Primitives()
End SubIn C#:
//TODO: Put this code in the application's App.xaml.cs file.
protected override void OnStartup(StartupEventArgs e)
{
base.OnStartup(e);
//You do not have to access any of the class' members.
//The CLR will load the assembly when you instantiate a class from the theme assembly.
Infragistics.Windows.Themes.Fall.Primitives temp = new Infragistics.Windows.Themes.Fall.Primitives();
}When a command is attached to a ButtonBase derived control in a focus scope other than the xamDockManager™ control (e.g., a ButtonTool in the xamRibbon control), the command will not 'find' target elements that are in xamDockManager’s floating panes. This issue will be addressed in a future version or hotfix release of xamDockManager. This issue does not apply to target elements in docked panes.
When either xamCarouselPanel™ or xamCarouselListbox™ is used inside of a Tab control, the xamCarouselPanel or xamCarouselListBox control must be wrapped with an AdornerDecorator to ensure that the CarouselPanelNavigator remains visible as the active tab changes. Without the AdornerDecorator, the CarouselPanelNavigator may disappear when switching to and from the tab containing the xamCarouselPanel or xamCarouselListBox control.
In XAML:
<TabControl>
<TabItem x:Name="tabSample" Header="Sample">
<Grid>
<AdornerDecorator>
<igDP:XamCarouselPanel />
</AdornerDecorator>
</Grid>
</TabItem>
</TabControl>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. The inherited properties of the AxisLabels, for example Font Settings, Foregroud etc., will not work multiple times at runtime. The workaround is to create a new instance of AxisLabelSettings everytime you want to update the AxisLabel property.
In Visual Basic:
Me.numericYAxis.LabelSettings = New AxisLabelSettings()
Me.numericYAxis.LabelSettings.Extent = 40In C#:
this.numericYAxis.LabelSettings = new AxisLabelSettings();
this.numericYAxis.LabelSettings.Extent = 40;By default, in order to change any frozen property on axis.TitleSettings, you must first create a new instance of TitleSettings and assign it to the TitleSettings property of an axis.
Not all the properties of a control should be saved through the Infragistics Control Persistence Framework. A good example is the ItemsSource of many list-like controls. When persisting a control’s current property values, one would not expect the control’s ItemsSource to be persisted. For this exact reason, the following Ultimate UI for WPF controls implement an interface that causes the listed properties to be ignored by the Control Persistence Framework:
This is the list of controls and the properties that will be ignored by default:
When working with xamQRCodeBarcode™ control, be sure to include the following NuGet package reference to your project:
Infragistics.WPF.Barcodes
For more information on setting up the NuGet feed and adding NuGet packages, you can take a look at the following documentation: NuGet Feeds.
In order to increase the performance of the Barcode Reader, evaluate doing the following tweaks:
Minimize the number of symbols to read. You can do this by reducing the value set in the MaxNumberOfSymbolsToRead property
Increase the minimum size in pixels that a symbol could be. This can be done tweaking the MinSymbolSize property.
Reduce the size of the image that is passed to the Decode or DecodeAsync methods.
Limit the number of Symbology Types sent to the Decode or DecodeAsync methods.
Limitations
The xamSparkline control, unlike xamDataChart, does not support rendering single data point. At least two data points of numeric values are required.
Filtering through the xamGrid Filter Menu is disabled for UnboundColumn.