adding mulitple single lookups to change visibility issue

[jarredmonday]

Hello all,

Mu goal is to combine two d.b. (on the right) into one. This block has three branch layouts and has three boot options for each layout. My idea is to have a lookup for each layout to choose one of three boot options. I want to start with the Straight branch and add the others two when I understand the direction i need to go.

I have the rotate parameter to change visibility states per specified angles. My problem comes when I want to change from three options at the specified angle. (see block to the right for example) 

[Libbya]

You need to think of the two tables of the double lookup as having opposite roles.  One is the input table and will have as input properties the parameters that the user changes either directly (e.g. rotate parameter) or indirectly (e.g. an point parameter that is moved by a lookup).  The other table is the output table and has as input properties each parameter that you want automatically changed.  When setting up the tables you can then place each parameter accordingly.  The user changes the block by changing the angle of the rotate parameter and by changing the lookup value which in turn changes the boottype input parameter.  As a result of the user's selection, the visibility state is supposed to change and the appropriate flips are activated.  The Rotate and 'Boottype' are both changed by the user and determine the state that is to be displayed and so would need to go on the input table.  The Visibility parameter and the flips would clearly go on the Output table.  I'm not sure why you have Move01 in there.

As a piece of fine-tuning you will want the base location of any input parameters (rotate and boottype) to match the bridge lookup values for the default visibility state or else you will have the 'custom' option on the lookup menu.