The header text is forced to be the member:
plano::api::NodeDescription->Type
which is coupled with the prototype of the node.
This means every instance of a node type would display the same name.
In @adamsepp use case, the API was edited to provide nodes with a setNodeName() and getNodeName() callback.
This made other parts of the program be able to set the node name via the user, ultimately.
The header text is forced to be the member:
plano::api::NodeDescription->Typewhich is coupled with the prototype of the node.This means every instance of a node type would display the same name.
In @adamsepp use case, the API was edited to provide nodes with a setNodeName() and getNodeName() callback. This made other parts of the program be able to set the node name via the user, ultimately.