Hello,
There is a strange behavior of XamGrid (in WPF) when it placed into TabControl. Switch between tabs takes 1-2 seconds (for redraw). While XamDataGrid is faster in times.
Could you please explain the behavior described above and propose a solution how to decrease the time of switching between tabs.
Example is attached
I can say that the xamGrid releases all cells to avoid memory leaks, when it's unloaded. It doesn't know the difference between a tab switching vs. the control being remove completely from an application.
Hope this helps you.
I have a similar issue. I have a WPF tab-based application where the user often utilizes 10-15 grid in normal usage, and the memory usage just keeps piling up, i.e. the cells aren't released when switching between tabs. This is extremely unsustainable. Is there a fix to this? I tried setting the grid (xamGrid) visibility to collapsed or hidden but it doesn't work. Memory is only freed up when the entire application is minimized to the system tray. The issue is the same for the xamDataGrid as for the xamGrid. Please help me.
Could you please be more specific, what tool do you use to track the memory usage of your application, because the Task Manager’s indication is not very relative to the work of our assemblies.
Looking forward for your reply.
Hello Eric,
Could you please send an isolated sample project, where the issue is reproduced, so I can investigate it further for you?
I have a similar issue I'm dealing with. I have a WPF MVVM app where I'm dynamically loading tabs in a tabcontrol. In each tabitem I have a XamGrid that is bound to a DataTable object in the ViewModel. I am loading data and setting the SummaryDefinitions when the tab is selected.
The problem is that when switching tabs from one that has data to another that has data and I get a NullRefrenceException related to the DataManager class. If I switch to a tab where the grid has no rows loading, it works fine. After some experimenting I found that if I do not set the Summary info, the grids work perfectly. Somehow, the exception seems to be related to the way that the tabcontrol reloads it's contents and what the XamGrid is doing with summaries. Any help would be greatly appreciated.
Eric