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
{{ message }}
This repository has been archived by the owner on Aug 5, 2020. It is now read-only.
This is somewhat related to #5 and #10.
When a node contains too many children, clicking on it to expand or collapse causes a substantial shift of a tree. You have zoom out and search for the node you've just been looking at, which takes quite a lot of time. A solution could be in calculating x and y of a just-clicked node in two modes (when its children are hidden and visible) and then adjusting the global coordinate system accordingly.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is somewhat related to #5 and #10.
When a node contains too many children, clicking on it to expand or collapse causes a substantial shift of a tree. You have zoom out and search for the node you've just been looking at, which takes quite a lot of time. A solution could be in calculating x and y of a just-clicked node in two modes (when its children are hidden and visible) and then adjusting the global coordinate system accordingly.
The text was updated successfully, but these errors were encountered: