You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dynatree had something like tree.enableUpdate(enable) that returned the previous state, which makes it easier to restore in nested calls. It also forced a redraw on enableUpdate(true).
See http://wwwendt.de/tech/dynatree/doc/dynatree-doc.html
It would be good to have tests for it (benchmarks) so we can compare different approaches.
Instead (or additionally) to suppress rendering, we should also benchmark performance, when the tree root element is detached while adding nodes (see https://api.jquery.com/detach/)
The text was updated successfully, but these errors were encountered:
Poor performance can be observed if we are adding many child nodes to a node that is already expanded (currently empty nodes cannot be expanded, so at least one child must already exist).
This means
FASTEST: add nodes to a collapsed parent and keep collapsed
FAST: Add nodes to a collapsed parent, then expand
Equally FAST: Add nodes to an expanded parent, but wrap it inside enableUpdate(false/true)
(Brought up by @u-874: see #553)
Dynatree had something like tree.enableUpdate(enable) that returned the previous state, which makes it easier to restore in nested calls. It also forced a redraw on enableUpdate(true).
See http://wwwendt.de/tech/dynatree/doc/dynatree-doc.html
It would be good to have tests for it (benchmarks) so we can compare different approaches.
Instead (or additionally) to suppress rendering, we should also benchmark performance, when the tree root element is detached while adding nodes (see https://api.jquery.com/detach/)
The text was updated successfully, but these errors were encountered: