-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Sankey: add attributes node.(x|y)
#3583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 6 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
320a4c4
sankey: add attributes node.(x|y) and update them on drag
etpinard 3cba316
sankey: fix syntax
antoinerg 1a89a1e
sankey: reset node.(x|y) when grouping, test drag for every arrangements
antoinerg 370250e
sankey: in `snap`, separate overlapping nodes even if node.(x|y) is set
antoinerg 8ddfe7e
sankey: `node.(x|y)` honors uirevision
antoinerg 40fb223
sankey: call _guiRestyle via Registry + slight code simplification
antoinerg 65c7201
sankey: arangement defaults to `freeform` if node.(x|y) is specified
antoinerg File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
{ | ||
"data": [ | ||
{ | ||
"type": "sankey", | ||
"arrangement": "freeform", | ||
"node": { | ||
"label": ["0", "1", "2", "3", "4", "5"], | ||
"x": [0.128, 0.128, 0.559, 0.785, 0.352, 0.559], | ||
"y": [0.738, 0.165, 0.205, 0.390, 0.165, 0.256] | ||
}, | ||
"link": { | ||
"source": [ | ||
0, 0, 1, 2, 5, 4, 3, 5 | ||
], | ||
"target": [ | ||
5, 3, 4, 3, 0, 2, 2, 3 | ||
], | ||
"value": [ | ||
1, 2, 1, 1, 1, 1, 1, 2 | ||
] | ||
} | ||
}], | ||
"layout": { | ||
"title": "Sankey with manually positioned node", | ||
"width": 800, | ||
"height": 800 | ||
} | ||
} |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do all the possible values of
arrangement
have an effect of the node layout whennode.x
andnode.y
are set?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Short answer: only
snap
can overridenode.(x|y)
Long answer:
When
node.(x|y)
is set, the nodes are forced to sit at the specified locations except in thesnap
arrangement. When drag and dropping,snap
is the only arrangement in which we forbid nodes from overlapping so I made sure we keep honoring this promise.The goal of this PR was to make it possible to replicate any state accessible via drag and drop via
node.(x|y)
and hence allowing to export images.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, thanks for the info!
Could we then make
arrangement
default to'freeform'
whenevernode.(x|y)
are set? That way, a user that wants to programmatically tweak the node position vianode.(x|y)
can do so w/o having to worry about changing thearrangement
value.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 65c7201