-
Hi Andrew. Thanks for looking. I’ll try to create an isolated repro
-
OK, as I suspected, an isolated repro worked fine, so I guess this is some sort of interaction. I’ve removed all the styling I can see, but it’s still happening. I do have access to your source code, and I’ve got it reproing from source. Any tips as to where I should be looking? I’m not familiar with the codebase.
-
The source code can bee very beneficial! If you step into SciChartRenderer.cs you will see the main render loop. In here there are a number of quick checks – do all Series have a DataSeries? Do all series have an axis? Are all series valid for rendering? etc etc… If it bails out there, it returns an error code. What do you see? Is it passing through all the functions and going to RenderableSeries.InternalDraw correctly?
-
OK I can see it’s because DataSeries is null, so it bails out. When DrawLabels=true, I can see my XySeries
-
To be more specific, there is a RenderableSeries whose DataSeries is null
-
Ok so my question to you is … why is RenderableSeries.DataSeries null? Does this occur when DrawLabels is set to false? Or is there another reason? Perhaps it’s a binding error?
-
Changing DrawLabels to false causes this DataSeries to become null. When DrawLabels is true, DataSeries is set to my XySeries. A breakpoint in the DataSeries dependency property change handler shows that it is set to my DataSeries through the binding, and it is never set to null
-
There is nothing in our code which sets the DataSeries to null if Axis.DrawLabels is false. I can only think of … some kind of binding in your application, or, a binding error occurring. Have a look at https://www.scichart.com/example/wpf-chart-example-modify-axis-properties/ — in this example we have checkboxes for things like DrawLabels and it doesn’t affect dataseries