Releases: d3/d3-force
Releases · d3/d3-force
v0.6.2
v0.6.1
- Reduce the default link.strength on heavily-connected nodes (#30).
- Reduce the default manyBody.strength to -30.
- The link.strength and link.distance accessors are now passed the correct arguments.
v0.6.0
- Add simulation.fix and simulation.unfix (#27).
- Add simulation.alphaTarget (#26).
- Add simulation.alpha.
- Optimize and area-bias d3.forceCollide to improve stability (#24 #25).
- Change the meaning of simulation.alphaDecay.
- Change simulation.restart to not affect the simulation’s alpha.
v0.5.0
v0.4.1
- Fix bug in d3.forceLink initialization.
v0.4.0
- Change the default simulation.alphaMin to 0.001.
- Optimize the initialization of d3.forceLink.
- Remove d3.forceContain.
v0.3.0
- Rename simulation.start to simulation.restart.
- Add link.iterations and collide.iterations for more rigid constraints.
- Improve the stability of the d3.forceLink and d3.forceCollide forces.
- Increase the default link strength to 0.7.
- Decrease the default drag to 0.4.
v0.2.2
- Change simulation.tick to always advance the simulation by one step, to not dispatch a tick event, and to return alpha < alphaMin. (The tick event is still dispatched by the simulation’s internal timer, which can be controlled via simulation.start and simulation.stop.)
v0.2.1
- Deterministic initialization using phyllotaxis!
- Fix a bug implementing manyBody.distanceMin.
v0.2.0
- Changed force.initialize to take an array of nodes, not the simulation.
- You can now pass a radius to d3.forceCollide.
- The links argument to d3.forceLink is now optional and defaults to the empty array.
- The nodes argument to d3.forceSimulation is now optional and defaults to the empty array.
- Removed the start event from simulation.on.
- Fixed simulation.start, simulation.stop and simulation.tick; you can now tick manually.