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
What needs to be done to achieve this? #697
Comments
Good question. |
@tsouk, you need to kill forceAtlas and restart it every time you add drop something from the graph. The reason why you must do this is that the layout algorithm is very low-level for performance reasons and works on a FloatArray that needs to be reconstructed if the graph's structure changes. In the future, we'll work this out for you through events. |
Thank you for your quick reply @Yomguithereal! Event listening for changes in the layout would be amazing. Update: Yup, works. I might try the click-drag-add that @devkhan is looking for then |
Adding/dropping nodes/edges are the case where you need to reset the layout. Other cases should be safe (apart if you need to hide some nodes or change their position in spite of the layout). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Can something like this be implemented using sigma.js.
I know draggable nodes and force directed layout can be done. But my graph has >200 nodes, so ForceAtlas2 doesn't stabilize even for a long period of time. So, I found this and this was in d3.js.
Can anyone tell me if it is possible in sigma.js, if yes, what do I need to do?
I don't want how to do this but if anyone can tell what steps need to taken, do I need to implement a different layout algorithm in a plugin or what exactly should I do, it would be really helpful?
The text was updated successfully, but these errors were encountered: