Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
allow `d3.layout.force().chargeDistance` to take a function
See original GitHub issueA number of settings on the d3.layout.force() object are dynamic, like linkStrength, linkDistance and charge. They take a function, so the value can be different for each node or link.
This seems to not be the case for chargeDistance. Is there a reason for this? It would come in handy for me at the moment. I have a number of isolated groups of nodes with their own gravity and enforced bounds, but still with occasional inter-group links. Having the chargeDistance be limited to the group size of each particular node would help both performance and visible behavior.
Issue Analytics
- State:
- Created 9 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Composable forces have been implemented in d3-force for D3 4.0.
The charge is a global (many-body) force, so the charge distance can’t be customized on a per-node basis (or per pair of nodes). However, it would be possible to compose multiple charge forces that affect different subsets of nodes, such that each charge force is local to the subset. See d3/d3-force#2.