algorithmic modeling for Rhino
You can replace Rhino geometry with a VB/C# script easily enough. I think replacing is better than adding new objects and deleting the old ones as it maintains the attributes (layer, colour, linetype, arrowheads, names, groups etc. etc.) and also the object ID.
The problem is, when you replace the geometry Grasshopper will think that it's supposed to react to that. So you end up in an infinite loop of (import curves, modify curves, replace curves, import curves again since they just changed, modify curves, replace curves, import curves again....)
The same is true if you delete the original curves, it will cause Grasshopper to run the solution again.
It's possible to solve this problem but it will require customized objects that have unique behaviour. I.e., you cannot shoehorn this into a regular Component.
--
David Rutten
david@mcneel.com
Poprad, Slovakia
Hey David,
I kind of thought that this might be a pandora's box.
When you say:
"It's possible to solve this problem but it will require customized objects that have unique behaviour. I.e., you cannot shoehorn this into a regular Component."
A Farnsworth Parabox?
--
David Rutten
david@mcneel.com
Poprad, Slovakia
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by