SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and now iOS Charting & Android Chart Components
Please use the forums below to ask questions about SciChart. Take a moment to read our Question asking guidelines on how to ask a good question and our support policy. We also have a tag=SciChart on Stackoverflow.com where you can earn rep for your questions!
Please note: SciChart team will only answer questions from customers with active support subscriptions. Expired support questions will be ignored. If your support status shows incorrectly, contact us and we will be glad to help.
I’m not making any sense of the AutoRange behavior in version 2.x. First, the documentation lists choices of .Always, .Auto, and .Never, but Visual Studio IntelliSence tells me the choices are .Always, .Once, and .Never.
The behavior I want is for the data to be fully visible (as after ZoomExtents) initially, but then to response to rubberband zooming and double-click unzooming. “.Once would seem to be the logical choice, but this doesn’t work. Instead, I get a Y-axis range of 0 to 9.
p.s. I’m using MVVM, and I may have forgotten the trick to calling .ZoomExtents from my ViewModel.
The behaviour of Once (default) is the option you are looking for, but in your case doesn’t seem to be working as expected. As a workaround please call DataSeries.InvalidateParentSurface(RangeMode.ZoomToFit) from your viewmodel (or SciChartSurface.ZoomExtents()) after binding the DataSeries.
Consider SciChart needs to perform the following on startup when AutoRange.Once is used:
As you can see we’re second guessing our developers a lot in AutoRange.Once. If you want, we can pull this out and just have AutoRange=True, False and leave it up to users to zoom extents manually or have fully autorange (where they cannot zoom via the mouse).
Finally, in all of our examples we don’t witness the behaviour you’re describing (of range getting stuck at 0..9) so I expect you’re doing something different to us, like showing a chart then later adding data, am I right? It’s possible this is a use-case we haven’t covered so if you can help us reproduce it, I’d appreciate it.
In the meantime please use a workaround (zoom extents after append) and you should be back in business.
Please login first to submit.