@LukasTonne any reason they are called "node socket panells" rather than "node panels"?
The scope of this is a bit unclear. It started out as panels to organize sockets, if it's supposed to…
I think these should be called "panels" rather than "socket categories"
I'm ok with "panel" too. It's a UI term, but since UI layout is the only thing we're going to use it for i think that's…
Ideally i'd like to display the node tree declarations in a way that resembles the final node output, to make it more intuitive. The vertical UI layout of the node editor sidebar makes that a bit…
Not sure, we may want to add more settings to categories, such as options to close categories by default, doc strings, etc.
Not needed any more, sockets now store category UID instead of simple index, so category changes don't require remapping.
Ok, i'm dropping it then, can revisit when we can actually do this in C++.
Sure, I'm just not sure that returning a pointer instead of a integer value helps prepare for
BitVectormore. Maybe until we can make this a C++ callback, it's better to use the value? It's…
I want to add a simple int identifier to categories, so that after adding/removing/moving categories i can remap the expand flag bits. Otherwise these category actions will mess up the…