SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and iOS Chart & Android Chart Components

Welcome to the SciChart Community Forums!

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 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 am developing a Xamarin iOS application and I’m using a SCIPieChartSurface. I can create the chart and set its values, but is is not possible to auto-update the donut with new data.
I am trying to update the value by doing:

myDonut.MyPieSegment.Value = newValue;

But nothing happends…

I heard it was a bug in the API for Android a month ago, is this similar? Or am I doing something wrong?
Thanks in advance!

Best regards

  • You must to post comments

Hello Jonas,

Thanks for reporting this. It looks like an issue in sciChart and I’ve already created task in our bugtracker, so it will be fixed in one of our future releases.

As for now, what you can do – is manually trigger redraw by calling invalidateElement on your series like below:


That’s it. Sorry for inconvenience. Hope this is suitable for your needs.

Best Regards,

  • Jonas Olsson
    Hello Nazar Sorry, but this workaround doesn’t work either. I’ve tried to run the InvalidateElement-command on both the SCIRenderableSeries and its SCIPieSegments-objects. It makes no sense. myDonut.MySeries.InvalidateElement(); myDonut.MyPieSegment.InvalidateElement(); When do you expect to solve this issue? Best regards Jonas
  • Nazar
    Hi Jonas, in that case I would ask you to provide some code which reproduces this issue, because I can’t do that locally in our examples app. Also, I can’t give you any ETA for resolving this issue, since we have working workaround for now. But for sure it will be fixed in on of our future releases. Best Regards, Nazar
  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.