algorithmic modeling for Rhino
I got tired of always zooming in and out of the definition in order to display different visualisations and or analysis results of the same model. Constantly turning previews on and off.
So I built myself a quick-and-dirty preview gate, which allows me to select which "Custom Preview" is shown. The check list is the "Value list" component.
Tags:
Comment
If you use Data Tree Branches you don't need to have multiple copies of the same components. At its basic level the image below depicts: All of one type of Object per branch. A material/colour per Branch. Use [Split Tree] to divert everything to be previewed and its material/colour to [Custom Preview]
for example on of the categories I normally use differentiating viewable objects:
Transverse Web Frames on {0}
Longitudinal Girders on {1}
Deck Platting on {2}
Shell Plating on {3}
Also you should have a look at Andrew's Human Plug-in for the [Dynamic Value List]
Hi Danny,
thanks! The definition pictured here is just a simple representation of the idea and in this very simplistic way, your implementation is arguably more intelligent. However, the need for this kind of solution came from a much more complicated definition and the previews can not be distinguished by different geometric elements.
They are actually more or less the same model, with just different coloring - based on some analysis (length, no. of connections, directions, etc.). Hence, the categorisation by copy-paste was kind-of the best solution for me.
But as you showed, the idea can be extended much further - hopefully eliminating the zoomin-zoomout-previewoff-previewon behaviour. :)
Mmmmm...interesting idea, let's think about it a little bit :)
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2025 Created by Scott Davidson. Powered by
You need to be a member of Grasshopper to add comments!