Bug: Cluster and Hoopsnake - The selection is interupted

Replies to This Discussion

Permalink Reply by Andrew Heumann on August 13, 2013 at 9:33am

Since hoopsnake breaks the normal left-to-right data flow in Grasshopper, it is natural that this error should occur. Yannis has already bypassed some of these "safety features," so presumably he can do this for the cluster check as well. However, you can easily get around this by disconnecting your desired cluster components from one side of hoopsnake before clustering, and then reconnect - the resulting cluster will work with hoopsnake just fine. 

Permalink Reply by phillip on August 13, 2013 at 10:04am

Thanks.

I already figured so and that´s what I meant with "it collides with the idea of an explicit history." .

So the reason I posted this here is, because I was wondering, as you describe:

Is it possible to create a bypass for a global criteria like clustering within a component (Hoopsnake)?