Hi,
I'm Building a demo App with the XamDataChart, I have 32 LineSeries linked to observablecollections and refreshing data each 100 ms with 15 new DataPoints per Serie, with the databiding, the updates are so fast and the chart do not render properly, I read an XamChart post with a RefreshEnabled property, the XamDataChart have a property similar/equivalent to perform refresh of the chart manually.
Thank you in advance.
HI Graham,
Thanks for your reply. I already have found a work arround for this problem. I turned of Notifiactions and make a class derived from obserbable collection. And this class is containing explicite rest for my collection Bellow is the method in which I am resting my collection after updating all the point and its working fine now.
public
CollectionUpdated()
{
.Reset));
Yes,
If you turn off the markers you will see the performance improve further, so it definitely seems as if we have an issue in WPF in that regard. I will get back to you with a bug number.
If you run the program in debug mode and have verbose binding errors on in Visual Studio, then the performance will seem much worse than it actually is due to the amount of binding errors being logged into the console adding a lot of overhead. Compare to if you run the program with Ctrl-F5, and then compare to when you run the program with the markers disabled.
-Graham
Because your items implement INotifyPropertyChanged, if you update them all every tick, then the chart will have to refresh that many times every tick. We are working to support that use case better in the future, but for now if your usage is to update the value of every item like that you are better disabling the notification events while you do the mass update, or detaching the collection while you change the items and then reattaching.
Unfortunately even if you do the latter, it seems like there is still a small hang each time the chart refreshes. I see a lot of binding errors being spit into the log that are not generated in similiar situations in Silverlight having to do with the markers. So I think there may be a bug for us to track down that is affecting the WPF performance in this scenario.
Hi Graham,
Please find attached a sample application of my senario. Thanks
Thanks for your reply and for the example as well. Can you please provide me a sample application. Actually I am using MVVM pattern and my collections are getting update through wcf call backs. Can you please provide me a running sample using MVVM updating collections in background worker thread? Currently I am doing in the same way and getting this GUI hang problem.
Thanks.