From what I understand ScrollBox is cannot hold nearly as many elements as ListView. In my last experiment i managed to add over 150 000 elements to list view and keep my fps over 120, while 1000 elements inside ScrollBox was enough to get noticeable drops. Furthermore, operations on ScrollBox children are really heavy and cause fps drops even with relatively small number of children.
So what I want to know, what can the ScrollBox do that ListView cannot. Is there a case I shouldn’t use the latter? Any hidden costs I should know about?
Scroll Box
is simple to use, perfect for simple thingsList View
is not as simple to use, setting it up might be an overkill if all you want is 10 items to scroll through.
Choose the right tool for the job. Would you create a List View to scroll through 7 static images?
Any hidden costs I should know about?
It seems more complex to manage. But if you already know how List View operates, this is not a cost. The flexibility and performance payoffs arrive quickly as things grow in scope.
1 Like