warmhug
commented
7 years ago This situation we know, tell the truth, because we are based on react, so want to make a full-featured and better performance treeview, compared to the use of jQuery will be more difficult.
it would be helpful for simple actions such as select or expand to only update the relevant nodes.
This is a good idea, can consider dividing the data to implement this built-in. But may be able to use dynamic loadData API to achieve at present.
Another problem you said, when you set x=500, y=5, z=1, The select action is very slow. You can also set it like this x=1500, y=0, z=1, thus there are only 1500 total nodes, but also very slow. So, i have already specified this in the document, it's here
So, please confirm that whether your pr really solve the problem.
In addition, because the tree and tree-select associated, if you modify the tree code, please be sure to test whether the tree-select is working properly, and in reverse.
cc @yesmeck
naderm
n7best
edencorbin
tomzacchia
erselnordlys
gs-vkinti
It seems that the way that rc-tree renders Tree makes minor updates (such as expanding or selecting a single node) very slow for large trees. This appears to be optimized in the case of deep trees (i.e. many elements hidden behind folders), but not for shallow trees (fewer elements, not hidden by folders).
A simple case be shown with the big-data example. When using x=5, y=500, z=1, there are 1252505 total nodes, but selecting elements is still snappy. When using x=500, y=5, z=1, there are 15500 total nodes, but selecting elements can take up to a second to update.
This might be a no-fix, but it would be helpful for simple actions such as select or expand to only update the relevant nodes. Otherwise interacting with the tree starts feeling laggy above 500 nodes, which seems small compared to other frameworks' TreeViews...