Message 1 of 1
why does get_Geometry() often contains a null Solid?

Not applicable
03-13-2019
07:48 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I often use the get_Geometry(DB.Options) function, and often it results a GeometryElement that contains one GeometryInstance, that contains a list of things, the first one of which is a DB.Solid with no faces and no edges. What is the use of this first (empty) solid ?
Also, ff the object contains an actual solid, the real solid is the last one of the list (Jeremy showed pieces of code where he gets that solid from the last object in the loop). Why is that ?