Property table and parameter grips

[Anonymous]

I could use some help here. I have a dynamic block with 3 move actions, 2 flip actions, a rotate action limited to 4 angles, and a visibility parameter w/ 2 settings. I want the 4 angles and the 2 visibilities to control everything. I setup a property table to set all the parameter combinations for the 8 desired configurations.

I get the desired results except that I want to be able to manipulate the parameter grips to get the desired configuration. Right now, as soon as my table get all the combinations in it, the parameter grips are no longer showing.

I tried doing away with the property table and going to lookup tables but was unable to get what I wanted.

Any suggestions?

[Libbya]

Post the block.

[Anonymous]

Here. I included 2 versions of the block. One shows the effect of the angle grip on the revision table but doesn't move the attributes into position with the visibility change. The other has the property table move the attributes into position but I lose my angle and visibility grips because I defined both in the table.

Thanks again.

[Libbya · Accepted solution]

I believe that what you are saying is that you want the positions/ visibility of the 8 options of the lower block, but want the selection options of the upper block, correct?  

There are a couple of ways to accomplish this.  I included both in the attached file.  They both use a linear parameter to shift the attribute up or down depending on the desired position.  I made the visibility parameter have grips=0 and added a lookup in its place.  On the lookup I switch BOTH the visibility state and the text position up or down.  The block properties table is left alone.  

The other way to do it would be to delete the block properties table and use a double lookup in its place.  The double lookup would have the angle and atttribute distance parameter as inputs and adjust the flips and Xmove on the output table.  

[Anonymous]

Thank you for the help. I ended up getting in to work using a similar method as you did with the property table and single lookup. Instead of using a distance/move parameter/action to move the attributes for the single line setup, I used a flip parameter/action with the flip line located midway between the desired positions. My lookup table then controlled the visibility and flip movements.

[Anonymous]

I was checking out your 2 blocks you modified for me. Well done. I was wondering though, on the double lookup version, how does the angle change cause the flip actions. I don't see the angle parameter listed on either lookup table.

I am curious because I like knowing how others have solved problems. Maybe I could use it in the future.

I also have another more general question about DB's. Say you have attributes grouped together with a point/move with an angle parameter to change the location. Is there a way to change the text alignment of an attribute automatically? When the attributes are at 180­°, they are right aligned; 90° or 270°, centered; 0°, left aligned.

It would make it easier then manually changing the alignment based on the rotation of my blocks.

[Libbya]

There are three lookup tables in the 'double lookup' version.  One lookup table is associated with the table/extra line selection and the other two lookup tables are associated with the gripless lookup parameter.  If you are not seeing all three tables, it is probably because you have the BACTIONBARMODE system variable set to 1.  If you change it to 0 you will see all of the tables.  The 'double lookup' is a lookup parameter that has two lookup tables associated with it.  They are one of the more useful tools within the stock dynamic blocks arsenal.  If the conditions of a row on one table are met then it will force the conditions of the parameters on the other table with the matching row name (provided the other table allows reverse lookup).  This accomplishes the power of the block properties - "must match a row" but with greater flexibility.  In that block, the input table of the double lookup has the angle and linear distance (that moves the attributes) as input properties and the output table has the flips and horizontal moves.

I don't know a way to dynamically change the text alignment of a given attribute, but you can simulate that behavior using fields, visibility states, and a double lookup linked together.  Here's a screencast that shows a couple ways of doing it.  One uses an invisible attribute to house the value, the other uses a user parameter.  In either case a dynamic action must be performed to 'jump start' the attributes.  Changing the value of the user parameter is a dynamic action so it automatically updates with a regen.  In the version that uses the invisible attribute to house the value, you need to hit the rotate grip.  In either case, after the value has been changed a regen is required to update the field.   

[Anonymous]

Thanks for the instruction. Very helpful.