Hello Kike,
The larger script is used to create large-scale assemblies and document the sub-assemblies with layouts and appropriate annotations on each detail view. I need for each sub-assembly to be isolated in on each page and for each detail view to only display the annotations needed for that view, and for everything to be visible in model space.
To accomplish this, I’m using Drafthorse to generate the layouts, baking the ModelObjects with attributes I can find later, then assigning the RhinoObjects the appropriate detail view Guids under AddHideInDetailOverride based on its ModelObject attributes. I know the ModelObject component in Grasshopper has a visibility setting for layout pages, but I also need to hide certain annotations in certain views, so it seems insufficient.
I’m not sure if it’s possible to modify the geometry in the way I need it modified before baking, so I currently need to bake as a halfway point in the process. Regarding GHPlayer, another solution in my case may be to use ContentCache and check “Keep open after command completes” as I’m using HumanUI (haven’t tested this), but looking ahead baking mid-command may become necessary if the user should need to create geometry to generate an assembly with.
For future reference on the “Keep open after command completes”, this was helpful (thanks for the post Kike).
Sorry for the verbose response, let me know if you have any other questions.
~CH