Alexithemia

@jacksonneal I'm still working on it but I think I found a method that should work. You can create a map to locate the nodes even after they are removed...

@canbax I'm not really creating a function to get all the children, I am simply adding the node objects to a node map I have created for other uses as...

@maxkfranz Restoring the nodes works perfectly. I'll add tests for checking after adding them with and without parents. There is no error when adding a node to the graph that...

I'll work on the tests, and I would probably just add it with a warning. From what I have seen while testing, it does not cause any errors or problems...

> @Alexithemia, are you still interested in this feature? Sorry about the delay! Really busy with things at work, and they put the need for this on the back burner....

@git3dGraph007 Were you able to make any progress on this, I am having the same issue.

I'm doing this with my implementation of the graph. This graph has a graph2ScreenCoords method that can translate the location of the node that comes back to it's correct screen...

It's part of the library, there a force pushing everything away from each other to make room while the engine is turned on (which happens during dragging). This doesn't affect...

Sort of addressed in my issue #232 Simply this happens because dragging the node reheats the force engine and the engine will not turn off until you release the node....

The issue may be center then. Make sure you are nullifying the forces like this. ``` myGraph .d3Force('charge', null) or myGraph .d3Force('center', null) ```