Hi BoucherS,
By setting the CanContentScroll style to true, is this mainly doing UI or data virtualization, and should ColumnVirtualization be enabled separately?
In the case of a statically declared table, if virtualization is enabled, would it still have to load in everything. I only suggested this because I seem to recall people suggesting putting things in static resources as a way to help improve the performance of WPF, and this way, I wouldn't be adding/removing columns dynamically.
For the full version of the control with the Batch update, can you explain how this could potentially improve the performance here? I may try to pitch this idea.
Also, as an aside, does the Extended WPF Toolkit contain any other controls that might be more suitable for the purposes of replacing a simple grid where columns may need to be added or removed frequently.
Thanks!
By setting the CanContentScroll style to true, is this mainly doing UI or data virtualization, and should ColumnVirtualization be enabled separately?
In the case of a statically declared table, if virtualization is enabled, would it still have to load in everything. I only suggested this because I seem to recall people suggesting putting things in static resources as a way to help improve the performance of WPF, and this way, I wouldn't be adding/removing columns dynamically.
For the full version of the control with the Batch update, can you explain how this could potentially improve the performance here? I may try to pitch this idea.
Also, as an aside, does the Extended WPF Toolkit contain any other controls that might be more suitable for the purposes of replacing a simple grid where columns may need to be added or removed frequently.
Thanks!