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

Introduce Annotations ItemsSource property

Available in Release Version Q1 2016.

Add the option for having separate PanZoomBars for each axis, so the user can scroll/zoom each axis independently from the other axes.

ChartView: Add support for axes rendering, when no data is available

As a workaround add a series with one point and set its color to transparent.

<telerik:ScatterLineSeries XValueBinding="."
                  YValueBinding="."
                  Stroke="Transparent">
    <telerik:ScatterLineSeries.ItemsSource>
        <x:Array Type="system:Int32">
            <system:Int32>0</system:Int32>
        </x:Array>
    </telerik:ScatterLineSeries.ItemsSource>
</telerik:ScatterLineSeries>

If two or more data points from the same series have the same X value - it should be possible to show information for all of these data points in the track ball.

Support for displaying error bars

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.

Add support for BoxPlot series type either through enabling extensibility of the CandlestickSeries type, or through providing new built-in BoxPlot series type.

Currently when sampling is used to generate the data points, the DataItem property of the DataPoint is null and there is no way to find out which data items have been used to generate the data point. A new property can be introduced (DataItems) which can contain the data items in mind.

Available in R1 2017 Release

Extend ChartSelectionBehavior to support continuous range selection through drag&drop.

When this mode is on - all of the points for which information in the track ball is shown should be on the left hand side of the mouse.

Set the DataContext of a Candlestick to be the DataPoint to allow binding to properties of the business object.

When this mode is on, information should be displayed for all data points in a given category (as opposed to displaying the closest points taken from different categories).

I would like to be able to create a histogram where both the x and y axis are linear series and where I can specify the start and end position of each bin (not just one). Previously described workarounds include using StepLineSeries and bar series which cannot have two linear series. I cannot use a scatter plot series as they do not provide the step-wise look of the histogram.  Please add this support! 

Add support for ScatterBar series type i.e. bar series that is plotted against linear / logarithmic axis.

When SnapMode=TrackBallSnapMode.None the IntersectionPoints should be drawn not over DataPoints but over the real intersection between series and TrackBallLine (also the TrackBallControl should display the real calculated intersection value itself).

XAML Team reviewed this request and decided not to address it in the future.

Add RangeSeriesDescriptor

Allow for the Polar chart to have multiple polar axes so that a user can easily understand what value does a data point have. For example a polar chart with four axes (with the same range) and an axis in each quadrant.

Currently, the control relies on its IsLoaded property to determine if it should render its items (axes, data points, annotations, etc.). However, if you measure and arrange the control in code without adding it into the visual tree, the IsLoaded property is not set to True, therefore the chart is not rendered and the image gets empty.

Original description
----------------------------------

Title: RadCartesianChart incorrecly rendered

We're rendering (Telerik) charts in code behind, to include them in a dynamic documentation.

For most controls it works fine - using standard methods (rendering control with System.Windows.Media.Imaging.RenderTargetBitmap and saving the result BitmapSource to disk)

However, it's impossible with RadCartesianChart with CategoricalSeriesDescriptor or ChartSeriesDescriptor. What we are able to get are axes and descriptions, but not bars.

I'm attaching an example - MainWindow displays a chart. I try to also create the chart in code behind. 
In CreateAndSaveChart() method I create a chart with a DataContext, then I call Measure and Arrange methods on it. At this stage the control should be properly initialized and ready to render. (For simplicity I omit rendering control with RenderTargetBitmap - you can preview the control with WPF Tree Visualizer, which will give you the same result). Well, if you preview the control at this stage, you'll see that the chart is missing bars. 
Next I create a new Window with my chart as a content, and display it for a while. Now the chart is fully and correctly rendered. As a workaround we display some Telerik chart in a transparent window to fully render, but such a workaround was reported not to work for some clients and is unacceptable in a long run. With most of Telerik charts we don't have such problems.

Other issue:
- for other Telerik charts we need to wait a few seconds to have it fully rendered. It's be better to have an event informing that the control is ready. 

I'll be happy to add more details if you need any.

* While experimenting with the example I've suddenly managed to render the chart with bars, but this time the rendered size was incorrect (very small)