Skip to content
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

layered: Assign model order on import of hierarchical graphs. fixes #724 #756

Merged
merged 8 commits into from
Sep 15, 2021

Conversation

soerendomroes
Copy link
Contributor

Simply set the model order when importing a graph (also for hierarchical graphs).

Signed-off-by: Soeren Domroes [email protected]

@soerendomroes soerendomroes requested a review from uruuru June 22, 2021 12:41
@soerendomroes
Copy link
Contributor Author

@uruuru Depending on the merging order either #717 or this PR must be changed (the other PR renames properties), I suggest merging the other one first and change this one accordingly.

@soerendomroes
Copy link
Contributor Author

Since #759 also sets the model order for the ModelOrderCycleBreaker this has to be updated either in that PR or in this depending on what is merged first.

@soerendomroes soerendomroes merged commit 26f62dd into eclipse-elk:master Sep 15, 2021
@soerendomroes soerendomroes added this to the Release 0.8.0 milestone Mar 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incompatibility between hierarchyHandling:INCLUDE_CHILDREN and considerModelOrder:NODES_AND_EDGES
2 participants