You’re right. So use Eneroth Solid Tools or BoolTools2. They respect components.
This has been a complaint of mine since the native Solid Tools were released. At 3DBC in Vail, I got to talk with the author of the extension and he agreed that there’s a problem. Unfortunately there have been more pressing fixes and features that have precluded changing them. Fortunately there are alternatives.
I have no use for SketchUp as a BIM application but I still want the Solid Tools to treat components the way other tools treat them when they modify them. As they currently are, the Solid Tools create more work for me than they save. Thanks to Eneroth3 and Dale for their versions of the tools.
Thanks for the reply, I’m basically an “experimenter” now that my CAD/BIM Management career has ended, so these issues are much more on my plate. I’m glad there are alternatives, I just hate having to recommend Extensions to my clients which have to be maintained when changes could be made to the main application.
Unfortunately, changing the native behavior might break the 3rd party extensions. It’s a “catch-22”.
What would need to happen is for the API methods to remain as is “under the hood” and/or expose a new non-destructive functionality with an extra method argument. (Ie, old behavior by default, new behavior by explicit option.)
The user UX could do the same with a Preferences option to set the default native tool behavior.
I do understand the sentiment of this, in wishing to keep things simple, and I also wish many extension functions were native. But extensibility is a huge part of SketchUp and many of the specialized functions they allow are not all realistic to be included off the shelf. Just saying Extensions are really worth exploring because as good as SketchUp is, it really starts to cook when you incorporate extensions. Version migration is a bit awkward with extensions, but really just an hours work once a year, small price to pay.
I am well aware of the power of extensions (having used SketchUp since day one). I often make Extension recommendation lists for my clients. Having a version migration tool would make things easier to manage.
Yeah, You have to be conscious of the current context and with the right shortcuts assigned, it’s not a big workaround.
In Bim, every component is wrapped inside a larger context, one level deeper does not make a difference, you all teady need another approach of entering (outliner)
Data on objects is better handled in Trimble Connect with the property manager, IMO.
If everyone used the same software , it would be easy
Using an outer wrapper or double wrapper where the top level holds all the data has another advantage. You can easily swap the lower level for another door type or window type, for instance. All the data is then preserved .
Pinging Philip @pcmoor
If a component can be saved as a little SketchUp file and having ‘raw geometry’ in a model is considered ‘bad modelling’, each component should consist of at least one group.
You can try Eneroth Solid Tools. They have a weaker algorithm that sometimes fails with complex geometry and are probably a bit slower, but they honor components, material inheritance, attributes, axes and so on.
If you want to swap a DC with a different type and wish to update any of the native attributes, then you include the CURRENT formula in the saveas DC, even though latter it maybe overwritten and it must have a sub-component of the geometry that references them.
If you wish to swap any sub-component then you must have a matching custom attribute and use the generic parent! as a prefix
It shouldn’t. You are just applying an invisible “data wrapper,” namely, the outer group. Attributes can then be attached to this outer group object without affecting anything about the stuff dwelling inside the group. Indeed, the objects inside a group or component don’t even “know” they are inside one. You can swap them in and out, or edit them at will.
As long as you don’t explode the outer group, its own attributes should survive, even if those of its child objects do not.