Hello!
We provide an option to our users to show/hide certain series. This is done by setting visibility of particular series to Visible/Collapsed.
Their ItemsSource is set to ObservableCollection, and sometimes this collection changes. And the problem happens when doing this:
1) User hides one of the series (sets Visibility to Collapsed)
2) Series changes
3) User sets Visibility to Visible
After this, series isn't visible! This problem happens only with the series that have been hidden, others are changing fine.
In fact, data is bound correctly, but the chart doesn't draw this series for some reason. This is confirmed by the fact that forcing the chart to refresh (e.g. zooming) instantly shows that missing series.
So, why is this happening? Is there any way to force XamDataChart to refresh explicitly?
Currently, I use a workaround: I set visibility to Collapsed, give time to draw a series using Windows.Forms.Application.DoEvents() (without this it wouldn't work), change series, and then set Visibility to Collapsed, but it isn't acceptable because the missing series "blinks" for a moment during this.
Best regards, Vasily.
Thanks for help.
Hi,
You will want to upgrade to either WPF 2011 Vol. 2, the latest service release or WPF 2012 Vol. 1.
We are no longer updating WPF 2011 Vol. 1. You may want to review this link for our service release schedule.
http://ko.infragistics.com/help/service-releases/
Now we are using 11.1.20111.2026 and discussing transition to 12.1.20121.1010. Are there any solution for these versions?
This was submitted as a development issue and was resolved with the WPF service release for 11.2.20112.2185. At that time the new WPF product version of 2012.1 was released and it did not have that behavior.
If you are using an earlier version you may want to apply the latest service release or upgrade.
Please let me know what product version and service release version you are using?
Hello
We have a situation that is similar to the one described in this topic. Is there a solution to this problem? Is this bug fixed in the latest version of WPF controls?