Hi @DavidRutten and @piac, I’ve adapted the TextGoo class. While the previewing is working fine, I have run into the following issue regarding baking, which does not happen all the time but only in certain cases. I’ve checked both types of components (the ones where Baking works, and the ones where it doesn’t), and there doesn’t appear to be any difference in the TextGoo code. However, when I try to bake any objects using, for example, the Move Shape component attached here, nothing happens, while it is still possible to bake geometry with S2G. I’m still getting back the geometry objects themselves, even with the components where no baking happens when I try to bake them.
I’ve attached the components here for your reference. Running them requires a custom external library and other custom scripted components that would require you to do some installation, so I’ll just post just the scripted components here for now since I don’t think the external library is necessary to illustrate what may be wrong in my code. Please let me know if you think otherwise.
bake_text_components.gh (7.2 KB)
What the components are supposed to do: Basically, in these two components S is a collection of data (coordinates, attributes) about line segments, text and points based on Rhino geometry, and it is turned back into Rhino Geometry through these components (which is why there is a G output). They’re stored in a custom data structure because that works best with the operations I want to perform on them (i.e. shape grammar, shape matching).
Thanks again for your answers, it’s helped me a great deal with learning how to script in Rhino (Python) better.