That’s a valid point. It’s essentially the same topic that’s already mentioned in the original post for instances. Currently, the gizmos only show for the first instance. In theory we could use different heuristics, but it’s likely something that needs to be user-configurable at some point. We don’t really always want to show the gizmos multiple times I think, as this could overload the viewport with potentially redundant information.
I haven’t implemented it explicitly for the Join node yet, but I’d assume that the earlier inputs currently have precedence over the later inputs.
Also see the last point of the gizmo section of our workshop meeting notes.
We generally want to retrieve the gizmos transforms from the geometry that’s shown in the viewport. I still have to support looking up the transforms correctly when the Viewer node is used.
If the transform output is not used, it’s also not part of a geometry that’s shown in the viewport, so it’s ignored.
It was called Gizmo in my original implementation, but we changed that at some point because the gizmo can exist without this output being used, and it’s technically only the “Gizmo Transform”, even on the code level. We skipped the “Gizmo” part of the name, because it’s redundant of the node name.
That could be implemented with the current design in theory, but it doesn’t seem to solve a problem so far.