A design time exception may be thrown in certain scenarios.

The Telerik.Windows.Controls.Chart.Direct2D.dll is missing from the nuget package file containing all Telerik dlls (Telerik.UI.For.Wpf).

If you set the PolarAxis.Maximum property to value which is equal to or less than the smallest value of a series, a DevideByZero exception is thrown.

Fixed in Q3 2014

When the application starts, the PointAnimation isn't played on PieSeries in a data-bound scenario. Also, this will hide the labels of the segments.

Will be available in Q1 2015 Release.

NullReferenceException on updating data when mouse is over chart's area and trackballinfo is visible. 

To workaround this, remove the TrackBallBehavior when data is updated and add it again on MouseMove.

CategoricalSeriesDescriptor.TypePath is not currently bindable. This means this has to point to a property on your DataSource that returns Telerik series types. This breaks the MVVM design model, as the DataSource points to the ViewModel, that should not contain any View specific types. Please provide a bindable alternative, such that a Converter can be applied to supply the View specific types.

Will be available in Q1 2016 Release.

Issue1) When no RenderTransformOrigin is set to ScaleAnimation, all slices should be scaled from the pie chart center point. Currently thiss is not true, to better reproduce it , set MaxScale > 1 and notice slices overlap each other at the end of the animation.

Issue2) When RenderTransformOrigin is set to , for example (0, 0), all slices should start animating from topleft corner of the chart. Currently only the first one is animated from top left and all others are animated from pie chart center.

The VisualStudio2019 ChartPalette (from Telerik.Windows.Controls.ChartView) throws the below exception when using the Telerik .NET Core assemblies. This does not occur when using the Telerik .NET Framework assemblies.

System.IO.IOException: 'Cannot locate resource 'visualization/palettes/resources/visualstudio2019.xml'.'
StackTrace:
   at MS.Internal.AppModel.ResourcePart.GetStreamCore(FileMode mode, FileAccess access)
   at System.IO.Packaging.PackagePart.GetStream(FileMode mode, FileAccess access)
   at MS.Internal.IO.Packaging.PackagePartExtensions.GetSeekableStream(PackagePart packPart, FileMode mode, FileAccess access)
   at MS.Internal.IO.Packaging.PackagePartExtensions.GetSeekableStream(PackagePart packPart)
   at System.Windows.Application.GetResourceStream(Uri uriResource)
   at Telerik.Windows.Controls.ChartView.ChartPalettes.LoadPalette(String fileName)
   at Telerik.Windows.Controls.ChartView.ChartPalettes.get_VisualStudio2019()

Fix available in LIB Version 2016.2.606.

The SelectStyle() method of the DefaultVisualStyleSelector is never called

Will be available in R2 2016 Release.

Available in LIB version: 2016.1.21

If you change the axes of a series at runtime in the following order the axis won't be rendered as expected.
1. Set the series' VerticalAxis property to a new axis instance
2. Set the series' VerticalAxis property to another new axis instance
3. Set the series' VerticalAxis property to the axis' instance created in step 1

This is observed in a scenario with two chart series and only the axis of one of the series is drawn incorrect.

When step 3 is performed, the axis is drawn at incorrect position. Then if you resize, the axis will be repositioned but without any ticks or labels.

Available in LIB Version 2015.3.1123.

The position of non-positive values cannot be determined when using a logarithmic axis (due to the nature of the logarithmic axis, non-positive values are undefined). Currently the chart displays such points as if the value of the point is 1, which is not correct. The chart should not display these values at all.

When the application starts, the PointAnimation isn't played on point series in a data-bound scenario.

Implement series descriptor for the chart's range series


Will be available in Q1 2016 Release.

In scenarios where a series is removed and after that an axis1 is removed, the other axis2 is rendered incorrectly if a series is added and then axis1 is added back.

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

NullReferenceException when MinorTicksPerMajor of the axis is set and the chart gets unloaded.

To work this around, avoid setting the MinorTIcksPerMajor property in this scenario.