Using arraycollection as a data source pitfall, there are almost no examples on the Internet, it depends entirely on your own exploration
In fact, using scroll bars to display tens of thousands of data is a garbage design. There is no way, the lvl is too low and it cannot be decided.
case 1：
There is an official saying: When using ItemRenderer's big data control, it does not create display objects for all data columns/rows at once (ItemRenderer) when rendering. It only creates data columns/rows that are visible on the screen, and reuses these display objects to submit runtime efficiency.
Therefore, it is easy to appear if the scroll bar is dragged or blank.
The reason is that the itemRender in Tree also causes delays.
Workaround: Call the() method in the scroll of Tree and refresh the tree.
case 2：
Automatically obtain tree data and no scroll bars are automatically generated when it exceeds the display range.
Solution: Distribute events after obtaining data.
(item);
(new CollectionEvent(CollectionEvent.COLLECTION_CHANGE, false, false, , -1, -1, [item]));
In fact, using scroll bars to display tens of thousands of data is a garbage design. There is no way, the lvl is too low and it cannot be decided.
case 1：
There is an official saying: When using ItemRenderer's big data control, it does not create display objects for all data columns/rows at once (ItemRenderer) when rendering. It only creates data columns/rows that are visible on the screen, and reuses these display objects to submit runtime efficiency.
Therefore, it is easy to appear if the scroll bar is dragged or blank.
The reason is that the itemRender in Tree also causes delays.
Workaround: Call the() method in the scroll of Tree and refresh the tree.
case 2：
Automatically obtain tree data and no scroll bars are automatically generated when it exceeds the display range.
Solution: Distribute events after obtaining data.
Copy the codeThe code is as follows:
(item);
(new CollectionEvent(CollectionEvent.COLLECTION_CHANGE, false, false, , -1, -1, [item]));