When you set the Palette property to a new instance of ChartPalette in XAML, a NullReferenceException is thrown. This happens when you click inside the chart control in the Visual Studio designer.
The exception reproduces only if the "Miscellaneous" category in the "Properties" pane of Visual Studio is expanded.
To work this around, set the Palette property in code:
Create 2-dimensional contour plot from unstructured 3-dimensional data. Means the points are randomly arranged in the XY plane. Attached file shows an example of what I would like to achieve. I think the contour plot Telerik does currently requires a structured grid, i.e. full grid of NxM points.
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.
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.
Introduce a way to set a geometry for the chart series' data points. Currently you cannot easily change the geometry of the default visual of PointSeries and LineSeries, for example. We can also introduce a default visual geometry selector.
An InvalidCastException is thrown in the Fill/Background property binding in the series' DefaultVisualStyle when the RenderOptions is set to Bitmap or Direct2D.
Add the option for having separate PanZoomBars for each axis, so the user can scroll/zoom each axis independently from the other axes.
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.
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 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.