Component wont save with a Tag

[haymaker]

Can someone please explain this to me.
If I have a component (boat) made from two other components (hull and Motor) both with separate tags and I insert boat into a model it will come in with both the tags associated with the components as expected. But when I insert either Hull or Motor as separate components they insert without their tags.
I Cant understand what I am doing wrong and its driving me nuts.
Thanks

Mike

[haymaker]

Ok, so If I edit the component and make a group I can assign a layer to the group and then it inserts ok. But this seems a weird work around and one that will bloat the outliner?
Is there a better way, why wont the component by itself hold on to the tag I assign it?
Thanks

[haymaker]

If I assign a tag to a face then the component will load with the correct tag but I thought it was not good form to assign tags to faces or edges. Why is this?
Still confused!

[Rich O Brien]

If Motor Component is in Boat Component and Motor Component has tag Motor it also has tag Boat. Because if you hide Boat tag then tag Motor gets hidden.

Not really hidden in terms of the tag in the Tag Panel getting toggled. But hidden because it resides in a tag that is hidden.

If you insert from Component Library Motor Component it can't have 2 tags because it is missing its parent container Motor Component so it is inserted into the Untagged tag.

[haymaker]

Hey thanks for your reply, somewhat helpful.
I still don't understand why I can assign a tag to a simple component like a box but then when I grab that component from the component library the tag assigned to it has disappeared.

[Rich O Brien]

@haymaker said:

I still don't understand why I can assign a tag to a simple component like a box but then when I grab that component from the component library the tag assigned to it has disappeared.

SketchUp doesn't differentiate between a saved model's component library and a system component library. I agree that it should know that the In Model component libary should respect whatever you have done In Model.

But its Global. So having components create Tags when loaded into a model some users may find that unintuitive. Moving a component to a Tag is a quick procedure via Entity Info.

Via Ruby API you could probably make a tools that does what you need. The beauty of extensibility!

[gullfo]

maybe it would be better to have a setting where component tags are added into the model or not (default). that way, may components tags could be added as i build up my model. today i simply have all the tags i generally use in my components already part of my default template.

however, if i have a blank template and want to incorporate those tags (and those nested in tag folders), there is no retention of the folders (i.e. tags don't know their parent tag folder) - so that would be a nice fix to add to the list. understood this is likely due to backwards compatibility, but it would be nice for those of us using the latest tools have the logic (and settings) to enable (or not) so we don't have to recreate the folders...