Grasshopper

algorithmic modeling for Rhino

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

GeometryPipeline-workaround.gh

Views: 2117

Replies to This Discussion

I too would love to see inputs on the pipeline... I believe David has expressed concern that dynamic inputs could cause some problems, and that is the reason they don't allow inputs at the moment.  I for one don't need them to be dynamic, so I would be happy with a "Use At Your Own Risk" pipeline component.

Marc

RSS

About

Translate

Search

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service