Add grid line style selector

PlotArea occasionally stops refreshing in live data scenario with asynchronous updates (multithreading).

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

Numeric axes should be able to specify their PlotMode as categorical axes do (currently numeric axes use hardcoded OnTicks plot mode).

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.

Expose RadFunnelChart and RadFunnelSeries for displaying funnel-like segments. They are usually used for visualizing stages in sales / marketing processes. 

Available in R3 2017 Official Release Version.
Check what's new in R3 2017 here: 
http://www.telerik.com/support/whats-new/wpf/release-history/ui-for-wpf-r3-2017

Available in 2014 Q3 release.

When the ItemsSource of a series is replaced with new collection, the labels of the old series are not cleared.

Fixed in LIB version: 2014.2.714

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/

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!

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. 

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.

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.

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.

The exception is reproducible when the chart contains series with RenderOptions=Direct2DRenderOptions.

The error message is:

HRESULT: [0x8876086A], Module: [SharpDX.Direct3D9], ApiCode: [D3DERR_NOTAVAILABLE/NotAvailable], Message: Unknown

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;