eris | Lavalink wrapper for the Discord API wrapper eris | Bot library

The line

extern int maxid = 0;

in the file ids.h is a definition, because it also initializes the variable. Instead, it should only contain a declaration:

extern int maxid;

The definition should be in a source file (.cpp), not a header file (.h). Header files should only contain declarations of variables, not definitions. Otherwise, you will violate the one definition rule if you include the header file more than once, or if you already have a definition in a source file.

In your case, you already have a definition of the variable in the file Tab.cpp. The line int maxid; is a definition, because it is not using the extern keyword. If you want to initialize the variable, you should do it in that file.

Generally speaking, we like to sanitize user input. You aren't doing that, and more importantly - you're assuming that the user is intelligent.

Your name choices are more naturally organized as Radiobutton widgets.

You can find the docs here. So how you would send it in a channel via a file would be

I think I have the solution for you. You have a problem in the reset button that is Reset. Here type="reset" main problem why you are unable reset data properly. So, you have remove that part from button and the button will look like Reset.
Note: I have tested some part of your code in stackblitz and my code working there. Please check the link Stackblitz Link

While I was not able to accomplish my task using matplotlib I came across a tutorial for plotly and dash while searching for the answer. There is one such wonderful tutorial here:

Plotly Line Graph Tutorial

Not sure if this is right way to do it using setTimeout. Its kinda hack, i may be wrong but it does work.

You would better create a dictionary with stocks as keys. See below:

I think a lot of what you did, specifically around data wrangling, was not necessary, especially since you called d3.hierarchy() and d3.cluster() afterwards. I've replaced this with d3.stratify (which deals with hierarchical data that is not yet in the right format).

I've also replaced d3.cluster with d3.tree() because it was unclear to me why you'd want to use d3.cluster here. Your data has multiple parents, multiple roots and even floating nodes, and d3 is not meant to deal with that. My workaround has been to attach pseudonodes to every level, so as to make sure that there is only one node and that all nodes are at the right level at all times. To make sure the links were drawn correctly, I've written a custom getLinks function, that can deal with multiple parents.

I've also written a custom link generator that draws the links somewhat in the way that you want them. d3 doesn't offer much of flexibility here, but you can use the source code for inspiration.

Edit

I've changed the logic to be more focused on which "partners" got a child, so both links to the same child are on the same level - like in your picture. I've also drawn the nodes based on how many partners they have, and have given every link an offset so the lines are more distinct.

I've sorted the nodes so that the real pro-creators are at the top (Zeus), which gives a more balanced and less crowded view.