I'm using UltraWinGrid.UltraCombo to display a table where the user can check/uncheck each row individually which works fine. But the header checkbox to select all/none items is extremely slow when the table contains a few thousand rows.
Am I doing something wrong?
I have attached a small sample project (VS2010) which demonstrates the problem.
Thanks in advance - and merry christmas :)
/Klaus
Hello Klaus,
I believe that this is expected since the 'UltraCombo' control is filling the 'CheckedRows' collection with every checked item after clicking in the header checkbox. This means that there will be a loop from '0' to '5000' items in your case. This collection has been added for comfort. If you want to have an immediate checking process of the items you might want to consider using the 'UltraWinGrid' control for that matter.
Please do not hesitate to contact us if you need any additional assistance.
Yes I'm aware that there's a 1-5000 loop where there is 5000 rows - but why is it so terrible slow?
On my PC, it takes more than 50 seconds!
Swithing to a normal grid is not an option - it needs to be a combo-grid.
Thanks Mike!! That solved my problem
Hi Roger,
It turns out that this was fixed way back in v11.2. But in order to "fix" this without breaking backward compatibility, a new property was added to the combo and you must set this property in order to improve the performance.
ultraCombo.CheckedListSettings.HeaderCheckBoxEventFiring = HeaderCheckBoxEventFiring.OnHeaderCheckboxValueChange
Even I have noticed the same in Infragistics in 15.1. We do plan to upgrade our infragistics to the greatest & latest for our product by the year end. However I have noticed that when the select all checkbox is clicked it seems to refresh the control by reading from the datasource for the update of each row. Hence if I have a combo with 5000 items it would refresh the list 5000 times looping through the list. As a result we would have 5000*5000 =25000 reads from the list. Can we have the combo to refresh the list after the select field is updated for all rows?Can you confirm if this is the case, I would need to get back to our business guys that this is a limitation as of now since there is no workaround.
I have tested the sample project attached above against the latest version of 17.2, and it does appear that this issue has regressed since 10.3 and is now reproducible again in 17.2.
This is unexpected behavior, and as such I have asked our engineering staff to examine it further. To ensure it receives attention, I have logged this behavior in our internal tracking systems with a development ID of 249585. I have also created you a private support case that will be linked to this issue so that you can follow its progress. This case has an ID of CAS-190901-C6Y4Z1 and you can access it here: https://ko.infragistics.com/my-account/support-activity.
I will be sending the initial update to this support case shortly. Please let me know if you have any other questions or concerns on this matter.
Sincerely,AndrewSoftware Developer
We recently updated to 17.2 and it's still an issue :(
Anyway you could look into it?