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

How to disable physics simulation? #8

Open
mbektimirov opened this issue Jul 21, 2014 · 4 comments
Open

How to disable physics simulation? #8

mbektimirov opened this issue Jul 21, 2014 · 4 comments

Comments

@mbektimirov
Copy link

Didn't find it in documentation and code. I use ngraph with fabric.

@anvaka
Copy link
Owner

anvaka commented Jul 24, 2014

Could you please tell me a bit more about your use case? Do you already have a graph layout?

@mbektimirov
Copy link
Author

I just need a static graph without any random movements. My graph is fully dynamic, nodes are loading on demand.

@alexbw
Copy link

alexbw commented Nov 3, 2015

+1

@gg4u
Copy link

gg4u commented Oct 21, 2017

I think that would be helpful possibility to allocate layout computation on selected communities of nodes.

I also load sub-graphs on demand, and actually much of the performance goes to adjust nodes that are not close to the areas a user is looking at.

Typically, the screen area.

I tried to pin nodes that are off the screen area and then free them as soon as they get into the visible are, but the result is not perfect: as soon as they get visible, the edges "rebound" cause all of the sudden forces are applied. And you see things moving around.

So I think that a good approach to test would be to apply forces proportionally to the distance of currently selected node: say, spring-force applied to n-th neighbors is set to 1/n-th, or with a custom function (I play with logaritmic adjustments now).

But don't have coding skill so advanced to modify the library (I am better at designing interaction and UX).

Or even simpler, it may be to turn on and off the layout engine.
Now, I found only layout.isNodePinned() as possible solution.
I did not found how to set "parameters" to "avoid" force-computation.

Alternatively you can use constant layout and set position programmatically for new layed out nodes - but please share if you find a good logic for expanded-on-demand graphs!!

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

No branches or pull requests

4 participants