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 have a real-time chart with a SciChartOverview attached. Since the chart series is being constantly updated as new data arrives, I must also synchronize the overview by adding new data to its series. I can throttle the chart drawing using SuspendUpdates, but the overview has no equivalent method. Keeping the overview up to date is therefore much more CPU intensive than drawing the actual chart.
I would like to request that you add a SuspendUpdates feature to the SciChartOverview in a future release.
Also, is there a way to set the maximum refresh rate on a chart and on an overview? Ideally I would like to be able to have multiple charts and overviews on a screen, and set the refresh rate for each of them independently. I can use SuspendUpdates successfully if there is no built-in mechanism.
From the release notes:
Limit frame-rate to a maximum Hertz, or leave null for default (unlimited).
Useful for strip charts (eg. CPU, Temperature monitoring) in process control
Note low values, e.g. 1, will not only limit redrawing but frame-rate when responding to mouse/zoom events
This allows limiting of the refresh rate of a SciChartSurface in Hz. The default value is Null, which means ‘unlimited’. SciChart will draw as fast as it can. A value of 24 can be used to dramatically reduce CPU overhead or 1Hz can be used to create strip charts.
Thanks again for the suggestion! Yes your feature request of throttling rendering is still in our backlog from last year believe it or not! It’s a good idea, what would be the API?
Something like this?
I think you can already do this which should reduce CPU load, as it puts the render-thread below the priority of mouse-input.
Please login first to submit.