Can someone explain what is happening here and how to fix this error? See screen shot. In this case the pdf is hidden - see tags. Not sure what’s happening here exactly and how to fix. Is it a grouping issue?
When I group linework (2d) I find that when I select it there is an ungrouped copy of the model “on top” of the grouped linework. Wondering why this is?
Keyboard shortcuts to select tools often don’t work at all. Wondering why this is?
Mike I just reread your message. I especially appreciate you pointing out that I don’t know what I’m doing. Such a helpful and positive fellow you are. Is it really necessary to say that or can you not help yourself to point out people inadequacies?
“All loose geometry should stay Untagged, unless you know what you are doing, which you do not, because you are here asking this question.”
And now you know and can address it. Not knowing something just means you can grow by learning about it and using it.
You clearly do not understand how geometry works in SKP. Assigning loose geometry to tags is a recipe for headaches, head scratching and questions like you posted. It’s basic stuff but until you know about it - how would you know? It wasn’t meant to be disparaging - it was meant to highlight that it should be reserved for use when you understand how it works. That is all.
You are not an idiot or stupid or whatever. You just need to learn how geometry and tags interact.
But I guess now every time you assign a tag to geometry you’ll think of that asshole Mike who purposely set out to ruin your day.
I 95% agree with you, although in some cases can be useful if you are aware of that and exploit such “weird” behavior to do some cool “trick”.
Probably the best solution UX-wise could be differentiating the 2 distinct behaviors (let’s say having 2 different commands such as explode to layer 0/explode to parent layer).
But, being that SU team is obsessed in keeping the interface simple and uncluttered in order to be user friendly, I get that there’s only an option. But then according to this philosophy it should be done as you propose, to better protect the user by himself.
