Community
Question: getSelectedLines() hangs UI
When using the getSelectedLines() function on a table with more than 5,000 rows and 32 columns (most of which are hidden), the UI hangs for a while (20-30 seconds) while it processes the function. If we have 10,000+ rows it hangs for over a minute.
Is there a recommended limit on the number of rows and columns a table should have so that the UI performance is not impacted?
Is there work around to get the number of selected rows without using the getSelectedLines function?
We are using v3.18 Patch 24 on RHEL 8.8.
Cheers
Eric
Responses (1)
I've used tables many times before and have never seen such an issue (on Windows). What i can imagine is that, in the click event in the table, you implement your own selectionmechanism. That is : in the click event you change the background color also updating an array with the index of the selected lines. That way, you wont need getSelectedLines()
Hope that is an option for you
Good Luck
Frenk