Hi, I am working on a number of UIs that will be using one instance of the XamDockManager to host various UI controls. Since we want a common look and feel, various user controls will be using the XamDataGrid control. A common use case is that the user will have two tabbed Content Panes in the XamDockManager, both of which contain a XamDataGrid instance, and will want to switch between the two. Sometimes, the user will even want to dock the Content Pane in a different location.
It is quickly becoming apparent that XamDataGrid is extremely weak at these cases out of the ox. Everytime a tab is switched, it takes over a second to render the XamDataGrid. Frankly, we begin to question the decision to use Infragistics. I have attached a sample solution that demonstrates the issues we are seeing. Try switching the tabs or docking one of the tabs using drag-and-drop. It's incredibly slow.
Short of not using the XamDataGrid, how can we get around this issue? How can we squeeze more peformance out of this?
Note: I am seeing the same performance characteristics if the XamDataGrids are replaced by XamChart instances.
Thanks,
-Szymon
There was a performance issue at one point relating to changing tabs when a control within the tab (e.g. xamDataGrid) had its Theme property set. If you have set the Theme then its possible you're encountering this issue which I believe has already been addressed in a released hotfix. If that is not the issue then I would recommend submitting the issue to the support group so the issue can be investigated.
Thanks for the quick response. Unfortunately, this is not the case. This sample is straight up out of the box XamDataGrid behavior. I might just open the support ticket.
Hello,
There was an issue regarding this and it is resolved now. Please make sure that you are using the latese service release for your versions.
Also, please mention the exact versions of the dlls that you are using so that we can verify that the issue is fixed with next version Service Releases.
Any luck with this? We are experiencing the same issue. Takes 2-5 seconds on large grids.