- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I know this is posted everywhere, but none of the answers use the method I'm trying to learn more about.
I don't think I can share the Block I am referencing here, due to the nature of the job. Basically, I walked in to someone's work and am SUPER curious how they made this happen. There is a block that triggers a stretch action and changes a linear parameter based on a lookup value, simple enough. There is a visibility state that adds more objects vertically stacked to said block. Sure, makes sense.
How can you have the visibility parameter change the lookup value though? There is only one lookup parameter, one lookup action attached to the linear parameter, it only references the distance (linear parameter), and the Lookup table has the same values as the visibility state, sans one where the lookup is visible in (hidden in all other states).
How might I accomplish this? I've been looking through forums, trying to replicate, whatnot. I understand the double lookup a bit better now, but given the nature of the job it would be so much easier to implement this method since it is driven by the visibility parameter and not the lookup parameter, meaning I can update, edit, and redefine blocks with values already in place and it will update the lookup value based on the current visibility state in the block (not having to go through every block set the lookup value to match the visibility state manually).
Anyone done this? Any advice on how it might be possible? Again, ONE lookup parameter, ONE lookup action attached to the linear parameter with a stretch action, ONE visibility parameter, and the table only has the distance (linear parameter) and a list of the same values as the visibility states (sans one). Reverse lookup is also enabled.
Solved! Go to Solution.