Your question is quite ambiguous, let me unfold some things first:
- It looks like you have a mesh primitive capsule for a cube in your scene. On it, you have an
ExampleTag. The capsule inlines the
BaseList2D representing the
Cube [Geometry] node, just as it is inlining its two tags Phong and Example Tag.
- You now drag a parameter from the capsule
BaseObject, e.g., its
P.X parameter, and are wondering why it behaves differently than the
Segments.X parameter from the inlined
BaseList2D representation of the
Cube [Geometry] node.
The answer to this is:
GraphNode and a
(Nodes)GraphModelRef are not the same thing, the latter is the graph while the former is a node in it. The
Cube [Geometry] is a node within a graph, not the graph itself. In the case of a geometry operator capsule this is hidden away from the user as you are not supposed to edit these capsules, but it still applies.
- Not every
BaseList2D representation of an entity inside a graph has a
NimbusRef. It is only the
BaseList2D which represents the graph itself, e.g., the
BaseObject in case of a capsule graph, which holds it. Which is also why I posted the screenshot from the Active Object plugin in my prior answer:
The representations of all entities in a graph are in a "Nodes" branching relation to the entity which holds the
NimbusRef for their graph.
- You currently can associate a
BaseList2D wrapper for a node in a graph with its
NodeGraphModelRef (i.e., "graph") but you cannot associate it with its
GraphNode, i.e., the actual node (in the public API).
Finde below my code example.
I compare here a
Mesh Primitive Group capsule and
Mesh Primitive capsule which is what you were using to clarify the relation of things. In both cases the "Cube" is just a node which lives inside the capsule. It is only that the
Mesh Primitive capsule inlines its geometry node because other than the
Mesh Primitive Group it is not editable.