4

I previously asked this question a few days ago, but I do not think anyone besides paxRoman actually figured out what I was asking, as it was hard to describe without an example.

We did however manage to figure out what might be my problem, and I managed to put the code up on bl.ocks.org so you can see an example of what I mean!

Here is the example: http://bl.ocks.org/3020018

Each time the data is refreshed (in this example, just read from a json file), all the nodes are re-created and re-added to the drawing.

What I want to happen

I want the nodes to update without moving at all.

If a new node exists in the new array, it should just appear like they all do now, if something exists in the previous array but not in the new, it should simply disappear.

As you see in the example, that is not what is happening and I have not been able to figure out why for the past week.

So my question is:

What am I actually doing wrong? Is it my lack of links? What is the problem? The two of us spent over an hour looking at this yesterday and could not make sense of it, I have spent a good week on it now without much progress :/

My old question/post is still up, but it's badly formulated and I had no example to show.

Thanks for helping me :)

Community
  • 1
  • 1
flexd
  • 819
  • 7
  • 17

2 Answers2

3

So, I am pretty sure I have solved most of my problems!

It came down to how I was adding/modifying the nodes when updating the data. I completely forgot about x/y and similar attributes since I did not set them myself, so I was adding "new" objects every time I updated the data, even if they weren't actually new.

With some jQuery magic using $.extend() I have sort of gotten it working, but it's still slightly moving/pulsing whenever I update the data.

I updated the gist to show the changes. http://bl.ocks.org/3020018

I would still like to remove that little pulsation too, so let me know if you have any ideas :)

flexd
  • 819
  • 7
  • 17
0

Have you tried setting the friction parameter (where you have the linkDistance and charge set)? Setting it to 0.9 will speed up finding the final position as I think it defaults to 1 if not set. Its simply a case of adding

.friction(0.9) // or any suitable value closer to 0 - have a play!

Hope that helps

LHB
  • 58
  • 5