Hi,
In my scenario i do not want virtualization on and hence I have switched it off by wrapping grid in scrollviewer, the performance is good when i am scrolling but the moment I add conditional formatting (via code behind) i see the scrolling is very slow. I used JetBrains dotTrace and windbg and can see the grid is recycling cells (See attached symbol). Can you please explain why this is so, the reason i turned off virtualization is because i have limited number of data rows (around 2000) and i do not want virtualization enabled.
similarly when i update the underlying data property, i see the below function slows down the UI phenomenally. As i mentioned there is no virtualization, the view port is very small, around 2000 rows and only 30 rows are visible with 10 columns. The performance etc is great when conditional formatting is not enabled, it works like a charm, but the moment i enable conditional formatting the whole grid struggles.
I see in the below stack trace, it is compiling dynamic delegate which is slowing down, is there any work around to improve the performance. The reason we choose xamgrid was because we expected performance would be better but this is not the case.
Appreciate your help.
THanks,
Rohit
Hello Rohit,
I have been looking into your issue and when enabling conditional formatting in the XamGrid positioned in a ScrollViewer, the scrolling works fine on my side. I am attaching a sample application() that I used for my tests. Could you please try the sample on your side and modify it if needed ? Also could you please tell me the version of our assembly files that you use like 11.2.20112.2316
Looking forward to hearing from you.
Hello,
Any updates on the issue? Did you try my last example?
Hi Rohit,
I have been looking into your concerns and if the ‘ShouldRefreshOnDataChange’ property is set to “True” makes the corresponding conditional formatting to be reapplied on all the cells, not only on the last modified. This is the design behavior of the control.
Let me know, if you need any further assistance on this matter.
I am sorry, but as per the documentation this is to be applied per row not "rows" across the grid.
So you are saying - If i have 2000 rows on my grid and row level conditional formatting is applied, and I add one row, we are going to repaint all rows/cells across the grid? If i am adding one row why are other row's cell style is being re-applied? Seriously, does it sound right to you? Because of this the entire core is maxed out when i add just one row.
Could you please double check this behavior with your development team. This sounds more like a design issue/bug to me rather "by design" behavior.
Alternatively: how can i apply row level conditional formatting to the newly added row to the grid (without repainting all the cells)?
I am just checking, if you need any further assitance on this matter.
I have logged this behavior with our developers in our tracking system, with an issue ID of 152229. I have also created a support ticket on your behalf with number CAS-122402-N5N4Q0 in order to link the development issue to it so that you are automatically updated when a Service Release containing your fix is available for download.
Yes Please.
Since this is a performance issue due to the limitation in xamgrid's design/implementation, do you think infragistics would consider this issue to be important engough to open up a case and fix this any time soon?
We need conditional formatting turned on and we add rows to our grid from external sources (I believe this is basic functionality for any grid), because of the performance reason as explained before, we cannot turn on conditional formatting auto refresh on.
Aside: As of writing this I have explained this to Kiril but haven't heard anything from him yet. Appreciate if we could at least open up a case to provide any other option to not repaint all cells but just for only the new row that is added to the grid.
I really want to use xamgrid but this issue is a blocker, we cannot freeze the UI thread for 3-4 seconds every time a new row is added to the grid.
Hope you understand the seriousness of this issue and will take it up with your dev team
Thanks much,