Thanks for the response Stefan.  Apologies for my late reply, I've been on a break!

I have multiple object collections that are used, one for each different series on the chart.  The X-axis will be of the same type, and in the case of a CategoryXAxis, will be based on the same data.  However, the X-axis values will not necessarily match up perfectly, i.e. you might have values A, B, C and D on series 1, but only A, B and D on series 2.

I've come as far as having them actually render on the same CategoryXAxis, but the values don't line up on the axis labels - series 1 will have values matching up to the axis labels, but series 2 will be sliglhtly off - value B drawn over label A for example.

I will try and get an example app going to illustrate.

Thanks,

Reinhardt

Sorry to revive this old thread - but I am beating my head against the wall on a similar issue.

We use these controls in a generic system, where the user can define his / her own charts using the generic data and layouts. In XamChart we had the ability to define multiple series on a chart quite happily, using completely disparate object sets per series. It seems to me that in the XamDataChart, this is not possible, as the bindings only cater for one (CategoryDateTime) X-axis, with the Y-axis values for different series coming from different properties from the SAME X-Axis DataContext?

In other words, using ChartDataPoint definitions as follows would simply not work if you have a collection of these for each series?

(simplified)

 class MyDataPoint { 
 object XAxisValue;
 object YAxisValue;
 }
 

You CAN ONLY define multiple series on one shared CategoryDateTimeXAxis using an object that looks like this:

class YourDataPoint {
 object XAxisValue;
 object YAxisValueSeries1;
 object YAxisValueSeries2;
 ...etc.
 }
 

Please let me know what you think - and for the love of all that is sweet and beautiful, correct me if I'm wrong, or give me an example of how I can use the first object and not have to use the second?

Thank you very much!