Hi,
I'm using an ObservableCollection to databind my xamWebGrid. When updating multiple items in the ObservableCollection, is there a way - for performance reasons - to suspend the databinding in the grid unitl the ObservableCollection is completely updated?
I.e. something like
_xamWebGrid.SuspendBinding();
... (updating the collection)...
_xamWebGrid.ResumeBinding()
Thanks,
/Andreas
Andreas:
Are you seeing performance bottlenecks when trying to update the grid via your observable collection? Our performance testing was very agressive, testing updates occuring as frequently as every 250ms. If you are seeing performance decline I would love to learn more about your scenario.
If you want to take this offline, you can email me direct at devinr@infragistics.com
Devin
Hi Devin,
I can't really say I've seen any performance problems yet - I just assumed they would come with increasing collection size. Seems like most grids have this suspend/resume binding pattern.
Every 0.25s is not very fast update if I'm adding a bunch of new items to an existing bound collection; the CollectionChanged method will fire a lot faster than that, right?
Anyway, I'll get back to you if I really encounter performance problems then :)
Andreas
Yes, please let us know if you encounter any performance problems. The grid has been designed to mitigate many of them.
Was there any resolution to this. We've got a grid bound to a VirtualResutlsColleciton<> and we're clearing it out and repopulating it. It works fine, but there is a NOTABLE lag (several seconds) to render the grid and we allow the users to put up to about 2 screens worth of content in before forcing them to page. If you scroll down through that content, it's a several second lag to get the page-rerendered.