Automatic axis range calculation should take into account the visibility of the chart series (i.e. the data points of a collapsed series should not be respected). Note: This is by design. The range of all series forms the range of the axis. If the user wants the collapsed series not to affect the range of the axis he can remove them.
If we set a Palette to RadCartesianChart and then modify the default StrokeThickness and Stroke of a LineSeries via Style, the new Stroke does not apply. The project attached demonstrates the problem.
The exception can be observed when you a plot data point with value that falls outside of the range of the Decimal type. As a workaround you can coerce the data before give it to the chart.
When the CartesianPlotBand annotation is bound to the vertical axis its 'From' value doesn't align with the axis. This changes when resizing.
"Insert" operation is not supported properly for chart series but is handled like "Add" i.e. RadCartesianChart.Series.Insert(0, series) will not result in inserting the series at zero index but internally it will be added to the end of the collection and it will be treated as last series. Available in version 2014.3.1215.
In a chart that displays more than one series, it would great to be able to turn on/off the trackball feature on a per-series basis. (Currently, suppressing the display of data for a given series doesn't prevent the trackball from snapping to points on that series - a weird experience for the user.
RadPieChart labels are clipped when RadiusFactor is 1.0
RadPieChart throws an exception whenever is in a DataTemplate of an ItemsControl with over 120 instances. The ItemsControl uses a RadUniformGrid as an ItemsPanel. Project is attached.
When a System.Windows.Interactivity.EventTrigger is attached to a ChartTrackBallBehavior a XamlParseException is thrown. A possible work-around for this would be to set the CommandParameter to be the parent collection of the behavior and not the behavior itself.
The fix is available in LIB Version 2015.1.0406.
When the values of the data points have great values and the axis has a very small manual range, the Path element does not render correctly and is at times not visible at all. Workaround: A possible way to resolve this is to use the Direct2DRenderOptions. The different render modes use a completely different rendering logic. <telerik:LineSeries.RenderOptions> <telerik:Direct2DRenderOptions /> </telerik:LineSeries.RenderOptions>
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.
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.
This is reproducible only when the chart's automation peers are used. For example, they are used by default when you use the chart on a touch screen. Or when an accessibility tool is used on the application with the chart. You can work it around by disabling the auto peers (http://docs.telerik.com/devtools/wpf/common-ui-automation). AutomationManager.AutomationMode = AutomationMode.Disabled;
The exception is reproduced only if the Visibility is initially bound to a property that returns Collapsed. This can be reproduce with the chart indicators that derives from LineIndicatorBase. For example, MovingAverageIndicator or MomentumIndicator. To resolve this you can bind the Opacity property instead of Visibility.
An InvalidCastException is thrown in the Fill/Background property binding in the series' DefaultVisualStyle when the RenderOptions is set to Bitmap or Direct2D.
This reproduces when the axis' SmartLabelMode is enabled. For example, set to SmartStep. See the attached video. As a workaround you can disable the smart label mode and manually calculate the range when zooming. You can use its Minimum, Maximum, MajorStep and MajorStepUnit properties.
Gaps appear between the bars in the stacks when the series are populated with negative and positive values. Check the attached picture. If you have a scenario with mixed values (positive and negative) use RangeBarSeries instead of BarSeries.
Some of the data points plotted in the chart are not positioned as expected in a scenario with DateTimeContinuousAxis with SmartLabelsMode=SmartStep and PlotMode=OnTicksPadded or BetweenTicks.