Allow Area ( and ScatterArea ) series origin to be set at a number, different than 0.

Available in Q1 2016 Release.

Allow Area ( and ScatterArea ) series origin to be set at a number, different than 0

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.

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 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.

Knowing where the cursor is and the associated coordinate and data information is critical to really create highly functional finacial chart. It allows the developer to overlay order tools on the chart like trendlines, possibly even enables the end-user to place an order directly from chart.

- Enhance cartesian chart interactivity by enabling the usage of TrackballInfo features without actually showing the trackball e.g. show the OHLC info in the top left corner of the chart (add mouse down/move events as well).
- Enable scenarios that need to pass trackball info to other charts e.g. on chart #1 you want to show trackball info for chart #2 at the same time (knowing the trackball info and coordinates of each chart is critical to syncing the track info of another chart that may be below the main chart as stock would want to see the tracking info for all chart simultaneaously).

Available in Q2 2015 Release.

Add support for automatic step calculation for the chart's axes.

Available in Q2 2015 Release.

The fix is available in LIB Version 2015.1.0406.

The fix is available in LIB Version 2015.1.0420.

An exception occurs in the VS designer when a RadPieChart is placed in a RadDocking's RadPane.

The fix is available in Q1 2015 SP Release.

Available in LIB version: 2015.1.1603

This can easily be resolved by using a Dispatcher.BeginInvoke to delay the adding of the element. 

The fix is available in LIB Version: 2014.3.1402.

"Insert" operation is not supported properly for chart series but is handled like "Add" i.e. RadCartesianChart.Series.Insert(0, series) will not result in inserting the series at zero index but internally it will be added to the end of the collection and it will be treated as last series.

Available in version 2014.3.1215.

Will be available in Q1 2015 Release.

Add grid interval property in order to control the number of grid lines with respect to the number of ticks on the axes.

Currently a grid line is positioned for each tick. Implement grid-line-interval property so that only one in n ticks have an associated grid line.

Add built-in support for smart series item labels i.e. automatic label arrangment that ensures the labels do not overlap.

RadPieChart labels are clipped when RadiusFactor is 1.0