generative modeling for Rhino
Geometry Pipeline Upgrade Request
I absolutely love the Geometry Pipeline, mainly for its event listening capabilities. Unfortunately I still have to use a workaround to get what I want out of it.
It is super helpful to be able to use a layer mask, for instance, but not very helpful to me to get all the geometry out in one flattened list. In order to retain that information, I tend to use the geometry pipeline only as an event listener, hooked up to a boolean toggle to trigger my VB script that reads layer geometry and outputs a path structure. (See attached.)
It would be great if the geometry pipeline had some path structure options (Path by Layer? Path by Name? Layer then Name? Name then Layer? Type?) or if it had a set of outputs that gave identifying information for each object (layer, name, type), which could be used to cull/structure data downstream. I trust you would find a clever way of doing it.
Thanks,
Marc
Views: 182
Replies to This Discussion
-
Permalink Reply by Marc Syp on -
Bumping this to the top one more time. Sometimes I make wishes and the desire subsides and I let them fall through the cracks. Not with this one. Every time I use the pipeline component (which is often), I pine for these upgrades.
Thanks,
Marc
-
Permalink Reply by David Rutten on -
Hi Marc,
didn't see this until now. Thanks for bumping again, I'll have a look, see if I can come up with something easy-to-use yet flexible.
--
David Rutten
david@mcneel.com
Poprad, Slovakia
-
Permalink Reply by David Rutten on
-
Just added two menu items, each of which complicates the data structure by an extra dimension:
There's no way to group objects by name or layer name using wildcards, I can't really think of a UI that would allow you to modify the grouping logic.
--
David Rutten
david@mcneel.com
Poprad, Slovakia
-
Permalink Reply by Marc Syp on
-
Brilliant! So I am inferring from your last comment is that there is no way to report out the associated layer name or object name in a separate output... anyway, this will work wonders for me, assuming that the layer names (and therefore paths) are ordered alphabetically. I still need to be able to correlate the data to specific layers, and as long as there's a predictable structure I can do that...
Thanks,
Marc
Translate
Search Grasshopper
© 2012 Created by Scott Davidson.
Powered by
