Cluster questions

New to trying this.... Is there any way to re-order the inputs? I seleted the part of my def that I want to cluster and it automatically sets everything up, but I would like to re-arrange the inputs.

Also - with the new slider takes on the name of the input it's connected to - when I have one slider connected to multiple inputs, they each get a cluster input (and several can have the same name) instead of being unified... I can go back in and edit them (painfully), but is there something I'm missing to get them to unify automatically?

Thx,

--Mitch

Added: also, if I have a cluster input I can't rename (it's locked on "0"), what did I do wrong?

Replies to This Discussion

Permalink Reply by David Rutten on May 19, 2013 at 11:16am

The higher the Cluster Input hook in the cluster file, the higher the input on the cluster object.

About the slider, you mean the name should be inherited from the parameters inside the cluster the slider is indirectly connected to? I'm confused.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Mitch Heynick on May 19, 2013 at 11:26am

Yeah, sorry, not easy to explain... Lets say I have a number slider and before clustering it's connected to the A input of two different addition components. When I cluster, I get two A inputs for the cluster and the slider is connected to both.

The hardest thing is if I have several sliders and they're all connected to an input like that, I get a bunch of "A" inputs on the cluster - and when I go into editing mode the cluster input components are all also listed as A, but it's difficult to know which inside A is connected to which outside slider...

Clear as mud, right?

--Mitch

Permalink Reply by Mitch Heynick on May 19, 2013 at 11:29am

The higher the Cluster Input hook in the cluster file, the higher the input on the cluster object.

Now THAT is an odd way to do things, but it does work!

Thanks, --Mitch

Permalink Reply by David Rutten on May 19, 2013 at 11:41am

I sort of liked the total UIlessness of this approach. I fully concede it's about as discoverable as the Higgs boson though...

As for your inputs, I definitely recommend merging them into a single hook. This is probably something I can do automatically, but for some reason I can't quite recall now I didn't when writing the new clusters.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Mitch Heynick on May 19, 2013 at 11:52am

Yeah, OK, thanks, done... Only one thing - I have two input names that seem to be locked (stuck on "0", I can't modify their names).. Seems buggy...

Permalink Reply by David Rutten on May 19, 2013 at 11:56am

Hmm, is the parameter they point to renamable?

It is a bug, renamability should probably not be inherited through a cluster.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Pieter Segeren on May 20, 2013 at 4:10am

I have that with the Math>Addition component: can't rename the inputs.

Permalink Reply by Mitch Heynick on May 20, 2013 at 4:26am

Yeah, that might be it, I think in both cases above where the name was frozen the cluster input was connected to at least one math addition component. However, to fix it, I just created a new input component inside the cluster editing environment, connected it where the old one was and deleted the original - then it worked...

--Mitch

Permalink Reply by Pieter Segeren on May 20, 2013 at 4:41am

I used to put a prepend a primitive in to obscure that the input was going into a Addition component (or whatever component), but since the cluster input properties can be edited nowadays, it won't show any inhereted discription or name anymore.

Permalink Reply by Daniël Smidt on November 30, 2013 at 4:31am

Any idea how to make the changes in the input properties reflect on the cluster component it self?
When I save and close my cluster the parent document shows the old names and discription on the cluster component.

Permalink Reply by Pieter Segeren on November 30, 2013 at 4:56am

I guess what you want is to double click the in-and outputs in the definition to be clustered, to change these discriptions. Right?

Permalink Reply by Daniël Smidt on November 30, 2013 at 5:06am

Thanks for the quick reply, but maybe I messed up my description of the problem.

It's no problem for me to change the properties of an in/output.

The only problem is that after that is done and I close the cluster editor canvas. The changes are not shown on the parent canvas.
See screenshot for example (L changed to CL and OL).

I guess this has something to do with the possibility to manually change the input/output names of every component. So you can also manually overwrite the cluster component input/output names.
What I want is the possibility to update the component input/output name/description to reflect the settings inside the cluster.

Attachments: