Fix typo in algorithm to correctly accumulate layout location for nested child nodes#87
Closed
konall wants to merge 1 commit intovislyhq:masterfrom
Closed
Fix typo in algorithm to correctly accumulate layout location for nested child nodes#87konall wants to merge 1 commit intovislyhq:masterfrom
konall wants to merge 1 commit intovislyhq:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The algorithm for computing layout was (I presume) mistakenly ignoring the location of parent nodes when laying out their children, causing nested child nodes to display from (0,0) even if their parents were located at some offset.
See an example of this behaviour in #58