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
In the example, Node, Link, and Pin share the same id incrementing mechanism. Can different types of elements have the same id? Will this cause problems?
If I want to display a general graph model through imgui-node-editor, does it mean that I have to create an additional ID mechanism for the graph to adapt to imgui-node-editor? Is there any recommended solution for this?
The text was updated successfully, but these errors were encountered:
Hello Yilin,
I discovered this library a few hours ago, so I'm really not an expert. I assume that you're talking about the "blueprints" example. IMO the example is, well, just an example, and you don't have to use the same id mechanism if you don't want to.
By the way, I've seen that in this example, the node builders (the SpawnSOMETYPENode functions ) return a pointer to an element of a vector. I recommend changing this, at least check the size of the vector and define a max value for id, or else there is a high risk of segfault.
In the example, Node, Link, and Pin share the same id incrementing mechanism. Can different types of elements have the same id? Will this cause problems?
If I want to display a general graph model through imgui-node-editor, does it mean that I have to create an additional ID mechanism for the graph to adapt to imgui-node-editor? Is there any recommended solution for this?
The text was updated successfully, but these errors were encountered: