Skip to content

Issues: d3/d3-force

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

15 Open 141 Closed
15 Open 141 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Opportunity for performance gains via d3-force-reuse?
#226 opened Jan 9, 2024 by Nantris
1
README links to deprecated notebook
#219 opened Jul 30, 2023 by hamirmahal
1
1
forceCollide ignores fixed positions
#213 opened Jan 9, 2023 by belukha
5
consider making .tick() reversable / accept negative iterations
#208 opened Oct 20, 2022 by jleonard-r7
6
Method to get all forces currently set (or at least clear them)
#203 opened Dec 23, 2021 by RLesser
Collide force doesn't handle identical initial positions well
#199 opened Jul 15, 2021 by Nate-Wessel
1
7
README has links to non-force-directed beeswarms
#194 opened May 7, 2021 by jtrim-ons
1
Iterative-Relaxation in d3.forceLink
#193 opened May 2, 2021 by gvarnavi
Accept iterables?
#178 opened Aug 28, 2020 by Fil
d3.forceLimit? idea
#169 opened Jul 9, 2020 by mbostock
Go back to position Verlet? idea
#158 opened Mar 15, 2020 by mbostock
1
Suggestion: add an angle property to d3.forceRadial() to define the forces in this angle
#152 opened Nov 7, 2019 by logomanwolf
1
6
d3.forceCollideRect?
#110 opened Jan 3, 2018 by martgnz
4
Consider adding a mass property to nodes idea
#96 opened Jun 14, 2017 by benstevens48
18
add d3.forceExtent
#89 opened Mar 10, 2017 by gka
1
2
ProTip! Updated in the last three days: updated:>2025-01-18.