Clustering Destroys Output

Replies to This Discussion

Permalink Reply by David Rutten on June 27, 2011 at 1:18pm

Everything should be clusterable so this must be a bug.

 

I'm going to work on clusters primarily for 0.8.0012 (or anyway the next significant release) so hopefully it won't take too long for this to get solved.

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Danny Boyes on June 27, 2011 at 3:23pm

I have the same problem.

 

Rhino v4, Vista 64-bit

Permalink Reply by Andrew Heumann on June 27, 2011 at 6:18pm

I have frequently had trouble clustering while retaining connection to other components. It always works if I connect the "cluster input" and "cluster output" arrows and leave no connected component deselected when clustering. (And works properly on your example file.)

Permalink Reply by Luis Fraguada on June 28, 2011 at 1:55am

I can verify that I have the same behavior as Andrew.  In order to make sure everything works, I have to use the Input Output arrows.  This is a bit nasty since I essentially have to copy the code I want to cluster, do the Input/Output business, cluster, and the connect inputs to the cluster.  Not so workFLOW friendly, but it does work.

Permalink Reply by Danny Boyes on June 28, 2011 at 2:57am

Yep this works, but there is still one quirk. After clustering there is a wire back to the origin of the canvas, after disconnecting it's normal so not a problem, but does this happen for you?

Permalink Reply by Andrew Heumann on June 28, 2011 at 1:20pm

Yeah there is always a wire for each input connected to the upper-left-most corner, which is bizarre, but doesn't seem to cause any problem. To quickly fix it I cut and paste it from the document - bringing it back without any such connection.