algorithmic modeling for Rhino
The type of data that flows through a wire is irrelevant, if it works for one it works for all. Here's what you should pay attention to when replacing wires with this sort of functionality:
There also some stuff about growing and shifting selections, but that is not essential functionality.
I use this method quite a bit and it works fine. As you probably know you can also share objects between different Grasshopper files using this method. The process of finding the target components to expire the solution is tricky though. You may have to find other ways to do that.
On a tangential note, I've also found that using cPickle with arbitrary structures of RhinoCommon-based objects is much more flexible and fast than storing geometry in .3dm files. You can create nested dictionaries of Geometry and any other serializable data and then just pickle it.
Hi Ben, What you mentioned sounds really interesting. Do you have an example file that you can share?
I used this previously to save objects that stored particular view states I can't remember what kind of class instance I was saving, but I remember that Steve Baer kindly added serialization methods to that class. I may have been storing viewport objects. It seems that pickle calls serialization methods on classes if they exist, so anything serializable should work fine. It's actually very easy (link to gist) (python docs about pickle)
here's a link directly to an example in the python docs:
Thank you Ben. This can be really powerful for moving the data around. Will give it a try tonight. -Mostapha