@chris fullmer said:

Thats how I end up with menu variables with names like this:

Aroofline
Btrim
Ccolor
[b]Dlength
E[/b]width
Fheight

And then if I need to insert something between A and B I do:

Aroofline
ATshingleType
Btrim
Ccolor
Dlength
Ewidth
Fheight

Yeah, its not my favorite method of organization 😄

Chris

An equally unfavorable way to re-organize sub components is to drill into the the parent shell (or whatever shell you want to organize), select and cut (not copy) the sub-comp, and right away do a "paste-in-place" without closing the shell. Do this for each sub-comp on the order that you want them to appear. Each time it is done, the cut-n-pasted-back piece will show up at the bottom of the list, at least that is how it is working on my Mac.

Matt

The way to do that is to make a component of each type of picket. Then they each need a hidden attribute asigned to turn them on or off. Then make add a user defined variable to the outermost fence component. Set it as "Users can select from list". Then it will give you a list that you create. Add a name for each type of picket. Lets say there are 3 picket types. Put them in the list like this:

Plain - 0
Rounded - 1
Ornate - 2

So now the user will see the name and can select what type of picket they want, and the menu will return a 1,2 or 3 as its value.

So now you have 3 separate picket components and a menu option for people to choose what type of picket they want. Now you need to hide all components that are not selected. Do this in the hidden attribute. (I need to mention that we'll use "PicketType" as the user defined variable that creates the menu item that the user selects).

Picket 0 should look like this:
Hidden - if("PicketType"=0,0,1)

Picket 1 should look like this:
Hidden - if("PicketType"=1,0,1)

Picket 2 should look like this:
Hidden - if("PicketType"=2,0,1)

That will set each picket component to be visible if the user has selected it from the list. If it is not selected, then it will be invisible. This will be set to all copies of pickets too (I hope).

So give that a shot, let me know if it doesn't work like I think it should,

Chris

i see, in these cases i always start from scratch - if you want, you can download my rubyset. it is a collection of many plugins (for pc but may work on mac) - maybe you'd find it useful.

http://www.quarr-it.com look in resources

(i'm also working on an updated set coming out sometime 'soon')

Could you, please, post this list in the ruby forum so that the authors of these plugins can have a look?