When you try to set the LabelDefinition property in style it is not applied.

As a workaround you can create an attached property to which you can apply the custom definition and set it to the LabelDefinition property of the annotation in its OnPropertyChangedCallback.

Depending on the zoom level and height of chart, sometimes the first (bottom) label of the chart is not rendered when the vertical axis is a categorical one and the plot mode is BetweenTicks or OnTicksPadded. 

The stroke property of the PaletteEntry is not respected.

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.

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.

You can observe the difference between the ChartView and an Excel Chart with the same data in the attached pictures.

When setting MajorTickInterval, the actual interval used in display is adjusted when zooming to show a reasonable number of ticks. However, if LabelInterval is used along with it to achieve the desired number of labels on the chart, LabelInterval is not adjusted along with MajorTickInterval, resulting in too many or too few labels being displayed. Moreover the automatic adjustment of MajorTickInterval cannot be disabled, leading to problematic label display that cannot easily be handled by the developer without inside knowledge of the algorithm. 

Nice features would be:
- Adjust LabelInterval along with MajorTickInterval to keep approximately the same number of labels on the chart.
- Given the above, add an option to allow the Chart to determine the optimal MajorTickInterval and LabelInterval by itself (currently if MajorTickInterval is not specified, it displays ALL category ticks which can be way too many for the display)
- Add an option to disable the MajorTickInterval automatic adjustment if the programmer wishes to handle this manually

This suggestion arose out of this forum thread, which includes an example demonstrating the issue:

http://www.telerik.com/forums/majortickinterval-trouble-when-zooming

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.

Create  a chartview with a linear axis, set minvalue to 2014-11-21, max = 2014-11-24, create a series with only one datapoint with a date=2014-11-23.
The barchart graph will show a nice bar, but the X-axis will show you 2014-11-21, although the datapoint is for 2014-11-23!

Allow to track points that intercept vertical line from mouse position (as now)  or points that intercept horizontal line from mouse position.
So allow to choose TrackDirection = Horizontal/Vertical

Thanks.
marc.

Implement an indication for negative areas in a single AreaSeries/RangeSeries. For example the negative areas to be drawn in one color and the positive areas in another.

For more information on the visual representation you can take a look at the following blog post:
http://peltiertech.com/area-chart-invert-if-negative/

The series are not rendered as expected when using Direct2DRenderOptions and hiding labels (by setting the LabelInterval, SmartLabelsMode or via a different approach)

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.

When a chart have long labels on the X axis (like date and time) the zoom is not accurate on the horizontal extents with both mouse wheel and drag area.

The reason is probably that the screen coordinates of the selected area are not mapped correctly on the X axis. The mapping works fine for tooltip.

 

You can verify this behavior in the attached Solution. In the images you can see the selected area (01), that the zoomed area is a region with no points (02) and the actual position of the points.

 

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.

Pan/zoom behavior should be configurable whether to execute its logic on right mouse button or left mouse button down.

More information regarding this functionality can be found in the Smart Labels help article.

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.