-
Notifications
You must be signed in to change notification settings - Fork 592
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
Fix the positions of some nodes/edges during rendering #64
Comments
Is there a plan for this ? I think it would be a useful addition and it might possibly help with #31 (comment) as well. I think the problem in general with re-rendering is that nodes' positions varies wildly, so in medium or large graphs it's hard to follow what happens. In some cases, even when adding/removing a single leaf node. |
I can imagine how we could specify relative ordering between nodes so that they don't shift relative to each other. In fact, the layout code can already do this, but IIRC there is no user interface to specify this. Pinning the coordinates for nodes is more complicated. The Sugiyama algorithm doesn't start setting coordinates until the last phase, after ranking and positioning has been done. |
I think that even just fixing the relative ordering would definitely help, sure. |
I'm thinking of editing the code to make this happen, but I'm not sure where to start. Could you please point me in the right direction ? Thanks |
Sure. In |
I had to make changes to dagre not dagre d3. I noticed this isn't being maintained so I have made changes in a fork of dagre and then have a fork of dagre-d3 to pull in the forked npm dependency. |
Any progress ? |
Is it possible to specify the position of some (but not all) nodes at fixed coordinates?
Ideally, I'm imagining this kind of input:
The text was updated successfully, but these errors were encountered: