I have 4 Ultragrids ( 380 rows and 42 columns) and PerformAutoResizeColumns take 28 seconds.
I 'use :
- GridPrice.DisplayLayout.Bands[0].PerformAutoResizeColumns(false, PerformAutoSizeType.VisibleRows); // 3min without Visible row only- The cells are Text and there is no editor- There is Calculator manager on grids but not used during resizing process- infragistics 13.2 but the problem was the same on 11 and 12.
Hi,
Does the problem occur every time? Or only the first time you call PeformAutoResizeColumns?
In a case like this, where you are using UltraCalcManager, the column cannot be sized until the calculations are completed. So what might be happening here is that calling PeformAutoResizeColumns is forcing the entire calculation network to completely calculate everything before any resizing can begin.
If that's the case, then I would expect only the first call to PeformAutoResizeColumns to be slow. Any subsequent calls would be very fast, since all of the calculations would already be completed. You could also verify my theory by disabling the CalcManager and see if that speeds things up.
Without UltraCalcManager this take the same time ( 25sec) and all the calls are slow ( the first and the other)
Thank you very much it is 100x faster !!
I've been looking at your sample project and I think the key factor here is your setting of the RowSizing property. You are setting RowSizing to AutoFree.
The reason the AutoFree setting has an effect is that every time you resize a column, the 'Auto' setting on the row means that there is a potential for the row height to change. So when you size the column, the grid is also re-calculating the height of the row, which of course takes all of the other cells into account and it's very inefficient.
I'm not sure there's anything we can do about this, but it seems like there's really no reason for you to be using RowSizing.AutoFree, anyway, so you could just remove this setting and leave RowSizing set to Default and everything works much faster.
Hello,
I have logged this issue with our developers. I have also created CAS-127533-Z8F6Z5 to track the issue.
I was able to reproduce the issue using your sample, so I have asked David to write this issue up for developer review so we can look into it in detail.
I made you a sample ( vs winforms solution): The code is simple but Ugly :)
I use :
- VS 2010 ( project work on 2013 )
- Infra 13.2.20132.1011
- .net 4 with .Net 4.5.1 installed
- Windows 7 64