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.

Sign up for GitHub

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

Jump to bottom

Setting FA2 #175

Closed
Anmo opened this issue Feb 3, 2014 · 3 comments
Closed

Setting FA2 #175

Anmo opened this issue Feb 3, 2014 · 3 comments
Labels
bug

Comments

@Anmo
Copy link

Anmo commented Feb 3, 2014

Hi,

How can I start FA2 with diferent settings, without changing the script forceAtlas2

The startForceAtlas2, shouldn't receive a parameter settings (or options), to be pass to forceatlas2.ForceAtlas2?

And remove the setAutoSettings.

Or I'm see things wrong?

Thanks
@jacomyal
Copy link
Owner

jacomyal commented Feb 3, 2014

Yep, it looks you're right on this one. I always use it with the default settings, and since @Yomguithereal and I are working on a new implementation using Web workers.

I'll fix the API this week, thanks for the report :)

@adkatrit
Copy link
Contributor

adkatrit commented Mar 6, 2014

++

@jacomyal
Copy link
Owner

Also, thanks to @adkatrit it is now possible to give options to ForceAtlas2 (#215).

A---- pushed a commit to A----/sigma.js that referenced this issue Sep 16, 2015
@sheymann
Merge pull request jacomyal#175 from Linkurious/fix/plugin/customEdge…
7597cfb 
…Shapes/174

Fix jacomyal#174: Hovers not working if edgeLabels plugin not here
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jacomyal @adkatrit @Anmo