Currently, the categories in the CategoricalAxis are ordered by the order of their appearance in the plotted data. Allow ordering the categories manually.
Add an API in the chart spline series (like a method override or similar) that allows you to calculate your own set of additional points that render the spline in the chart's spline series.
By default when the chart is zoomed in, the major step between the axis ticks is automatically re-calculated to match the new zoom level. Add a property that allows you to access the recalculated major step.
Add mechanism in RadCartesianChart to change the axis origin position. Currently, you can position it only top, left, right or bottom. Add an option to position the axis at an arbitrary position on the opposite axis. For example, to position the horizontal axis in the middle of the vertical axis or at value lets say 3.
Currently, the chart provides a selection feature where you can select data points by clicking on their visual elements (ellipses, bars, etc.) or setting the IsSelected property. Add a feature that allows you to select the entire series. This feature is meaningful when using line or area series and you want to highlight (select) the clicked series.
You can easily implement it by subscribing to the MouseLeftButtonDown event of the chart series and change the series' Stroke or Fill property.
The RadCartesianChart's series allows you to provide a collection of primitive types (like List<int>) to its ItemsSource which will render a proper chart, as shown in the Create Data-Bound Chart article.
Currently, this is not supported if you use the sampling feature of the chart (ChartDataSource). ChartDataSource can't work with collections with primitive types. Add support for this.
The chart series allow empty values, which means that if a data point has a null or NaN value there won't be a visual element drawn on the chart. The financial indicator (a type of chart series) support this, but because of their nature, if an ItemsSource is provided, the null values are threaded as zeroes (the number 0) during the automatic generation of data points. This is because, the data point values are calculated based on a function which includes a combination of the previous data item values.
Add a mechanism like a method override or a property that can alter this behavior. In this case, if the data item of the generated data point contains a null value, the visual element should be dropped (missing) as in the standard chart series.
Currently, you can customize the fill and stroke of the data point visuals using the DefaultVisualStyle property of the series. In the common scenario, you can use data bindings to data bind the fill and stroke of the corresponding element. Additionally, you can use the DefaultVisualStyleSelector for such customization. However, when the Direct2DRenderOptions or BitmapRenderOptions are used, data bindings and the DefaultVisualStyleSelector are not support. The bindings in the DefaultVisualStyle throw errors and the selector is not applied.
Add support for conditional styling. This should include support for data binding in the fill and stroke properties of the element from the DefaultVisualStyle, or support for DefaultVisualStyleSelector, or another type of API.
Currently, you can format the axis labels using the LabelFormat property. This allows the same format to display different label value for the different cultures when the UI culture is changed.
Add support also for the Language framework property in this case.
Add a mechanism that allows the chart to process only the data within the viewport. This should improve the memory footprint and the performance of the chart in scenarios with big number of data points.
Implement a feature that allows you to start an animation when the values of a data point are changed. For example, if you change the value on the vertical axis from 5 to 10, a smooth animation updating the visual element should be started.