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

Add support for 3D Series Type in RadChartView.

A RadCartesianChart3D was introduced with R3 2016. You can use its BarSeries3D to easily achieve the Manhattan chart visualization.

See the documentation: 
http://docs.telerik.com/devtools/wpf/controls/radchartview3d/overview
See the SDK examples: 
https://github.com/telerik/xaml-sdk/tree/master/ChartView3D/WPF
See the demos: 
https://demos.telerik.com/wpf/

When thousands of items are displayed, the tooltip and trackball behaviors may become slow, because of inefficient searching for the closest datapoints. Performance can be sped up by implementing a custom search and manually creating a ChartDataContext via the GetDataContext method.

Hi,

I worked with a lot of chart components for Wpf. I think Telerik offer the best charts architecture that allow to obtain great results in every scenario.

After years of use, I think is possible to  improve more the global architecture.

1) Series Dataset

Charts now works with Points. I think that a better solution require a more abstract structure as a virtual "Dataset".
A dataset reuire a type [conform to X axis], tipically X can be a double, a datetime, a label.
Dataset return info about poits, tipically:
- Min X
- Max X
Dataset return a DataContext that allow to draw chart:
- GetCloserX to an X value [Trackball/Lables...]
- GetPoints from/to [Pan/Zoom]

This approach is really more efficent and powerfull. In example you can simply define a Dataset as a Formula:

Dataset "CosX" based on doubles.
MinX=-inf
Maxx=+inf
GetDataContext from/to -> Return allways 100 points x, cos(x).

So you can obtain:

- Ultraefficient series using GetDataContext algorithms for specific cases, in example, ordered data.
- Trend lines using "Formula" series

2) Only one series, with subtypes.

It is really annoying change series type.
I think a chart must contains a series and this series can show Line, Area, Split Line, Markers, Columns...

To write a good "option panel" that allow user to set Line Thickness, Line Split or standard, Area opacity, Area Color, Marker Type, Marker Colors, Columns Borders... require today a giant work and elaborate code that add and remove serie, reassign points, set z-index, remove and add series in legend... with an incredible useless works in points.

3) More accurate axes definition.

Now Chart and Series expose Horizontal and Vertical Axis property.
I think this is terrible properties :-).

"Horizontal" and "Vertical" is depending chart orientation. Furthermore now, first X/Y axis must be set in chart, others in series. Moving series from an axis to another is really annoying: if new axis is first you must set is null else you must set it...

I think Chart must expose XAxesCollection and YAxesCollection. This collections must contains all X and Y axes.
Series [and annotation and every object that uses axes] must expose XAxis and YAxis as the Axis object or Axis index.

4) Chart orientation

Today a simple chart rotation require a lot of code. The developer must be invert Horizontal and vertical axes, change axes in series and annotations, zoom/pan stop to work...
When this is combined with point 2) problems the result is an nightmare.

I understand this require a big work and a lot of compatibility problems [Telerik already exposes two charts versions, three is probably a little bit confused].

But if Telerik obtains this features I think it become the most unattainable charts component producer of the world.

Decline reason: Most suggestions were tried in the old RadChart and they weren't working very well.

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

Add support for 3D Surface Series Type.

This feature is now available as part of the ChartView control since R3 2016 Official release. Refer to the link below for more information.
http://docs.telerik.com/devtools/wpf/controls/radchartview3d/series/surfaceseries3d.html

Add support for 3D Surface Series Type.

This feature is now available as part of the ChartView control since R3 2016 Official release. Refer to the link below for more information.
http://docs.telerik.com/devtools/wpf/controls/radchartview3d/series/surfaceseries3d.html

Ability to specify a cursor during a drag-to-pan operation. One way to work-around this is to use the attached property in the sample project attached here. 
This is the code needed to start using the solution:
<telerik:RadCartesianChart local:ChartUtilities.PanCursor="Hand" />

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.

XAML Team recently reviewed this request and decided not to address it in the future since the Smart Labels functionality was introduced in Q1 2014.

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 support for tooltip visualization over the continuous series segments (besides the current support for visualizing the tooltip over the actual data point / point mark).

Declined due to duplication with http://feedback.telerik.com/Project/143/Feedback/Details/113405-chartview-enhanced-tooltip-support-for-continuous-series-segments-line-area-e

Add support for tooltip visualization over the continuous series segments that would interpolate the actual value between data points.

XAML Team reviewed this request and decided not to address it in the future. Appropriate way to get this is to use the crosshair behavior.

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.

Decline reason: This item is duplicate of the following one:
http://feedback.telerik.com/Project/143/Feedback/Details/113364-chartview-expose-the-data-items-when-sampling-is-used

Introduce DesiredTickCount property for the DateTimeContinuousAxis.

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

We introduced the ability for the axis to change step based on its size, so that labels do not overlap and presently we see no value in having such a DesiredTickCount property (whats even more the axis already has a MaximumTicks property).

Provide a way to synchronize Trackball and Crosshair behaviors.

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

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