reheat | A red hot Node.js ORM for RethinkDB | Runtime Evironment library

I have a nested dictionary and I am trying to figure out a way to loop through keys to obtain key values only.

I added a context menu in my graph, where I can use my add and removal function. A node which receives connections can´t be removed, a alert informs the user. Further I can "endless" add nodes. Now comes the interesting "problem" part.

Case 1: If nodes are removed ordered from highest to smallest and a new node is added afterwards, its fine. For example, remove node 8 and add a new node anywhere. Or remove node 8, 7, 6 and add a node afterwards will be also fine.

Case 2: Remove a node, which is not on the last array position and add a node anywhere afterwards. The connection will break. For example, remove node 5 and add a new node on 3. The connection of node 8 will break.

I am getting mental with this issue.

I got a D3 graph in place. Where a click on a node should delete this node and the related link. A hover on each node will display the name of it. Further a console.log confirms the name of the node, which was deleted. The problem I got is, as soon as I try to delete a node which is not the last one from the array, the console confirms the deletion but the node just replaces another one. Where is my thinking mistake?

I am trying to get in touch with the D3v6. Functions which I used to work with D3v4 seems obsolete now or are in need of different constructor. Anyway I am trying to add a node during a simple click event. addNode()

The ID is generator by the length of the array + 1, further I pushing the element to the array and create/merge the new node. Afterwards the simulation is restarted and the alpha heated. Still no clue why I get such a result as shown. Its like the nodes freeze and the links are moving instead.

I got an D3v4 graph in place, where I can dynamical add nodes. My problem is that each added node draws the link above the selected node. Adjusting the z-index seems nothing to change. The addNode() creates a new link and new node for now. The node is a mix between hard coded and dynamical yet. Further I push the newly created link to the original graph array and the same for the node.

Any hints how I can fix the problem?

In following the addNode() I am using:

I have a text file which contains a line like this:

I'm trying to make Force-Directed Tree with React and it works. But I cannot modify "link strength", if I pass it outside component through the props.

Honestly, I can change "strength", but I need to append d3 svg to my react ref div after that to see the changes. And whole graph will be redrawn.

I find example by Mike Bostock. He advice to modify the parameters of a force-directed graph with reheat the simulation using simulation.alpha and simulation.restart. But I cannot make it works with react. Nothing happens.

Here is my code:

I am trying to modify the color of some nodes in the force layout using a color picker.

I haven't found any examples of how to modify the elements within the force layout without the events being triggered within/by those elements.

This example is updating the layout with buttons, but is only changing the data that is passed, and then updating the graph. The data I am using contains a "group" which determines the color, which is defined in the JS. Therefore updating the data is not an option, however updating the variable doesn't work either.

This question asks about updating forces/attributes of the simulation itself rather than its elements and the solution here did not work for me as reheating the simulation does not pick up the changed colors.

So I've been working on this for a bit of time now and I'm a bit lost. So at the bottom of directions I have steps and I have numbered my steps but for some reason the text from my xml is not being transferred over.

This is the XML file