When you set the Palette property to a new instance of ChartPalette in XAML, a NullReferenceException is thrown. This happens when you click inside the chart control in the Visual Studio designer.
The exception reproduces only if the "Miscellaneous" category in the "Properties" pane of Visual Studio is expanded.
To work this around, set the Palette property in code:
When you change series datapoints and then play ChartRevealAnimation the following InvalidOperationException might occur:
Cannot call the ClockController.SkipToFill method for a Clock that has a Duration or RepeatDuration of Forever, because this Clock will never reach its fill period.
You can try calling PlayAnimation in Dispatcher:
Dispatcher.BeginInvoke(new Action(() =>
If you define the chart in a new window and open it from the app main window, and then close the window, the chart stays in memory. This is reproducible only in a data binding scenario - the ItemsSource of the chart series should be set to a ObservableCollection<T>.
Additionally, the collection bound to the ItemsSource of the series should be still alive. For example, it can be defined in the view model of the main window that opens the window with the chart.
To resolve this you will need to set the ItemsSource of all chart series in the window to null.
The fix for this issue will be available with LIB (version 2019.1.204) scheduled for publishing on Monday, 4th February 2019.
When you try to set the LabelDefinition property in style it is not applied. As a workaround you can create an attached property to which you can apply the custom definition and set it to the LabelDefinition property of the annotation in its OnPropertyChangedCallback.
If the annotation and its label are out of the viewport (the plot area) and then use the PanZoomBar to scroll to it, the label is not displayed. It appears after the chart layout is updated (ex: resize or zoom).
On a desktop device the tooltip is shown when the mouse enters the data point's visual element. On touch device the tooltip should be displayed when you tap (or tap and hold) on the visual element. Currently, this doesn't work. To work this around you can implement custom tooltip behavior using RadToolTip and TouchManager. https://docs.telerik.com/devtools/wpf/controls/radtooltip/overview https://docs.telerik.com/devtools/wpf/controls/touchmanager/overview
During Series animation, the stroke of the AreaSeries (area, splinearea, scatterarea, steparea) is not animated.
The exception is reproducible when you are using SplineSeries with DateTimeContinuousAxis. You need to add data points to the chart with a gap between the dates.
When the points in a series consist of values including 0, DivideByZeroException is thrown. The exception is thrown while measuring the chart - the tick step is set to 0 and the index of the tick on the axis cannot be calculated. Workaround: Set the Minimum and Maximum properties of the Axis. Available in LIB version: 2017.2.605
A NullReferenceException is thrown when the Strategy of the series is set Available in LIB version: 2017.2.605
When a linear axis is used with the same ticks (ticks number and ticks position), and the same plot mode as a categorical axis (BetweenTicks or OnTicks) - the width of the bars is different and is slightly smaller with the linear axis. Available in LIB version: 2016.3.1017
The trackball becomes unresponsive in a live data scenario with more than one chart. The issue is observed in a scenario with a categorical axis and grid lines originating from it. The fix is available in LIB Version: 2016.2.829.
An exception is thrown in design time when a RadCartesianChart is inside a RadExpander and no-xaml binaries are used in combination with VisualStudio 2010.
Fix available in LIB Version 2016.2.606.
The Open and Close properties of the OhlcSeries' data points are not updated at runtime in a data binding scenario when you update the properties from the view model. The same applies also for the CandlestickSeries. Available in LIB version: 2016.2.606
Available in LIB Version 2015.2.907.
Automatic axis range calculation should take into account the visibility of the chart series (i.e. the data points of a collapsed series should not be respected). Note: This is by design. The range of all series forms the range of the axis. If the user wants the collapsed series not to affect the range of the axis he can remove them.