Components tagged, then grouped

Scenario:
You have 3 individual components all with same tag assignment. You create a group with these 3 components and the Group entity is listed as Untagged.

Question:
Is this by design since the newly created Group is actually treated as a new entity?

Yes. That’s by design. You could then give the parent group a different tag if you wanted. The parent group is certainly treated as a new entity.

Suppose you had a different tag on each of the components. You could control their visibility individually. If you create a group to contain the three components, it could be given a different tag which would allow you to hide all three components in a single click.

Prior to the advent of tag folders grouping components was a way to manage object visibility. For example in a kitchen you might have the appliances, each with a different tag, grouped together with another tag called “Appliances” put on it. You could then choose to hide all of the appliances with a single click on the Appliances tag or you could hide just the Fridge. Now I think tag folders are a better way yo manage that kind of thing. Avoids unneeded excessive nesting which generally makes it harder to work with the model..

1 Like