Currently if one wants to save a geometry to file, it seems to require hacks and workarounds due to the fact that geometries are not BHoMObjects. Without wrapping it simply does not work, while with WrapNonBHoMObjects setting set to true, the geometries pushed from GH come in as wrapped Rhino objects, not wrapped BHoM geometries. Although I see the reason for that on the code level, it does not make much sense from the user's perspective.
Following the above, I would consider implementing some workaround that would handle BHoM geometry primitives same as BHoMObjects, so that the script in the screenshot below was functional OOTB:
I was not sure where to log that particular issue, so put it in the general Adapter - please feel free to transfer if you find applicable.
Description:
Currently if one wants to save a geometry to file, it seems to require hacks and workarounds due to the fact that geometries are not
BHoMObjects
. Without wrapping it simply does not work, while withWrapNonBHoMObjects
setting set to true, the geometries pushed from GH come in as wrapped Rhino objects, not wrapped BHoM geometries. Although I see the reason for that on the code level, it does not make much sense from the user's perspective.Following the above, I would consider implementing some workaround that would handle BHoM geometry primitives same as
BHoMObjects
, so that the script in the screenshot below was functional OOTB:I was not sure where to log that particular issue, so put it in the general Adapter - please feel free to transfer if you find applicable.
FYI @IsakNaslundBh @al-fisher @adecler @LMarkowski