Hi alexchou194,
The framework calls the measureoverride methods and we currently have no ways of bypassing this. We need to know why is it called too often or why does it takes too much time to complete.
I think the best would be for you to send us a small sample showing the delay in the loading.
In the meantime here are possible reasons why the loading could take more time :
1) Virtualizing is disable (by setting ScrollViewer.CanContentScroll = False), ref : http://stackoverflow.com/questions/3724593/why-setting-scrollviewer-cancontentscroll-to-false-disable-virtualization
2) In TableView, virtualizing of columns is disable (by setting TableView.IsColumnVirtualizationEnabled = false), ref : http://doc.xceedsoft.com/products/XceedWpfDataGrid/#Column_Class.html
3) The height of rows and width of columns is small, showing more cells in the screen.
4) The template of the cells are big and complicated to build
5) The columns are added in code-behind one by one.
The framework calls the measureoverride methods and we currently have no ways of bypassing this. We need to know why is it called too often or why does it takes too much time to complete.
I think the best would be for you to send us a small sample showing the delay in the loading.
In the meantime here are possible reasons why the loading could take more time :
1) Virtualizing is disable (by setting ScrollViewer.CanContentScroll = False), ref : http://stackoverflow.com/questions/3724593/why-setting-scrollviewer-cancontentscroll-to-false-disable-virtualization
2) In TableView, virtualizing of columns is disable (by setting TableView.IsColumnVirtualizationEnabled = false), ref : http://doc.xceedsoft.com/products/XceedWpfDataGrid/#Column_Class.html
3) The height of rows and width of columns is small, showing more cells in the screen.
4) The template of the cells are big and complicated to build
5) The columns are added in code-behind one by one.