You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although it was part of a minor release, #124 is a breaking change.
In particular, if we follow the docs and set fx and fy to null upon drag end (as in Force Dragging III), then we're in for some absurd behavior when we call simulation.nodes on our next data update.
(See Directed Graph Editor for a complete example.)
Setting them to undefineddoes work, since isNaN(undefined) is false while isNaN(null) is true.
The text was updated successfully, but these errors were encountered:
Although it was part of a minor release, #124 is a breaking change.
In particular, if we follow the docs and set
fx
andfy
tonull
upon drag end (as in Force Dragging III), then we're in for some absurd behavior when we callsimulation.nodes
on our next data update.(See Directed Graph Editor for a complete example.)
Setting them to
undefined
does work, sinceisNaN(undefined)
isfalse
whileisNaN(null)
istrue
.The text was updated successfully, but these errors were encountered: