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
I started to use the dagre-d3 for visualisation of data similar to one of examples (the Sentence Tokenization). Extending this example to display a DAG instead of a tree was super easy, but I've lost control of an order in which edges leave a particular node. Is it possible to restrict it somehow? If not, could you point me where to start looking into your code? For my data the order of edges is quite important.
In fact, it would be the best if i could constraint nodes order too (position from left to right in top down graph), but as I understand, it is not possible at the moment (issue #25 ?).
Thanks
The text was updated successfully, but these errors were encountered:
It should be possible to add an order attribute to nodes and edges in the input graph to indicate to dagre what the ordering for edges and nodes should be. This information could be used in the order phase instead of the barycenter heuristic. The implementation should be much simpler than that required for #25.
I'd be interested in what drives the requirement for edge ordering if you're at liberty to describe it. I can already imagine several reasons for wanting to explicitly order the nodes, though.
Hi,
I started to use the dagre-d3 for visualisation of data similar to one of examples (the Sentence Tokenization). Extending this example to display a DAG instead of a tree was super easy, but I've lost control of an order in which edges leave a particular node. Is it possible to restrict it somehow? If not, could you point me where to start looking into your code? For my data the order of edges is quite important.
In fact, it would be the best if i could constraint nodes order too (position from left to right in top down graph), but as I understand, it is not possible at the moment (issue #25 ?).
Thanks
The text was updated successfully, but these errors were encountered: