FIX. RadChartView - Vertical Stripes go out of the chart area when PanZoom is using.

RadChartView -  sometimes Property Builder of RadChartView is setting HorizontalAxis to be LinearAxis and to VerticalAxis to be DateTimeCategoricalAxis when you select "Linear & Date Time Categorical " which leads to incorrect work of PanZoom.

Workaround:
Use Smart Tag instead of Property Builder or swap the types of the axes in Design file.

http://www.telerik.com/help/wpf/common-export-support.html

Resolution: 
Add an option to export the chart to an image or a stream using the ExportToImage methods.

http://www.telerik.com/help/winforms/chart-features-marked-zones.html

RadChartView - DateTimeContinueAxis ignores the MaximumTicks property with some specific data points. 

Steps to reproduce:
Use the following points:
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2007, 7, 24)));
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2007, 10, 30)));
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2008, 4, 29)));
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2008, 10, 27)));
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2009, 4, 1)));
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2010, 6, 28)));
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2010, 10, 7)));
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2011, 4, 19)));
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2011, 9, 27)));
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2012, 1, 10)));
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2012, 4, 11)));
            points.Add(new CategoricalDataPoint(r.Next(0, 100), new DateTime(2012, 10, 16)));

RadChartView - user should be able to enter minimum/maximum width for Bars in BarSeries.

RadChartView - Palette of the Series should be with higher priority than Area.View.Palette.

This problem is related to different serie types are added to the chartview

Currently values can only increase from left to right and from bottom to top.

When trying to drill down PieChart on RadChartView the code throws exception.

Workaround: private void radChartView_Drill(object sender, DrillEventArgs e){    e.View.Parent = this.radChartViewUsers.ChartElement.Wrapper;    e.View.AreaType = ChartAreaType.Pie;    //do drill logic}

We should add a way for users to bind a property in the data source that will be used as a legend title for pie data points.

Resolution: 

Set the LegendTitleMember property to bind legend title of PieSeries. 

SmartLabelsController - PieTwoLabelColumnsStrategy throws exception if the series has two or more DataPoints with value "0";

Code to reproduce:
            RadChartView pieChart = new RadChartView();

            pieChart.AreaType = ChartAreaType.Pie;
   

Currently, there seems to be no convenient API for formatting data point elements. There is a CreatePointElement event, which however does not work properly.

ChartLegendElement is not able to wrap the LegendItems

Steps to reproduce:
1. Add a chart to a form.
2. Add any cartesian series
3. Set the LabelFitMode of the horizontal axis to Rotate.

You will see that labels have incorrect layout.

Currently only axes labels can be rotated. There should be a way to rotate series labels as well.

Resolution:

Set the LabelRotationAngle property of the series to preferred angle. 

RadChartView should have empty values support just like RadChart had it.

Steps to reproduce:
1. Create an instance of any chart series
2. Set the Palette property to a new/existing PaletteEntry instance with any colors 

Run the project and you will see an exception.

Steps to reproduce:
1. Add a chart to a form
2. Add a bar series with some data
3. Set the gapLength of the horizontal axis to 0

Run the project and resize the chart. You will see that the gaps between bars are inconsistent.

Currently the axis data flows from left to right starting with the smallest values and increasing. There should be a way to verse this flow and the most left values to be the biggest.