Here's one more version. In this one, there is only one frame and one wipeout and a stretch action has been added to the point paramter that moves the attributes, in order to stretch the frame/wipeout. I also set the default to 1 level and wipeout off.
FWIW, that's not a simple block. For anyone curious, it is constructed as follows. The basepoint is moved to the callout area so that the positions of the attributes remain correct when it is moved. There is a point stretch for the callout area and another point stretch for the end of the arrow. Then it gets a little complicated. There is an 'invisible' point parameter whose initial position is 1,1 - the only reason for the 'invisible' point is to give input values for the 'bridge' lookup parameter (more on that soon). There is a 'wipeout' lookup parameter with a single lookup action for controlling the wipeout. That lookup has the two states of 'wipeout off' and 'wipeout on' and when it is changed, it moves the 'invisible' point on it's x-axis between 0 and 1. A second lookup parameter selects the level. That lookup has the selection options of 1-4. With each selection it simultaneously moves the 4 attributes to their appropriate position for that state, stretches the frame to match and moves the 'invisible' point on its y-axis to 1-4. There is a visibility parameter with the 8 visibility states that correspond to 'level 1 wipeout Off', 'level 1 wipeout ON', 'level 2 wipeout OFF', etc... The visibility states only affect the wipeout and which attribute(s) is(are) visible.
There is a 'bridge' lookup parameter with TWO lookup actions associated with it. Associating two lookup parameters is a little tricky, but a very powerful out-of-the-box option. To do so, right-click on the lookup parameter tool on the tool palette, click on the 'action' field, click on the '...' on the right and use 'add' so there are two lookup actions associated with it. The tool will then place a lookup parameter with TWO lookup tables. Setting bactionbarmode to 0 will let you see both of them. On the right side of the two lookup tables, the 'lookup properties' MUST match between the two tables. If they do, then the two tables will drive each other. In other words, when the conditions are met for a row on one of the two tables, the input properties of the other table are changed to match that corresponding row. The 'Bridge Input' table has the input properties of the 'Invisible X' and 'Invisible Y' linked to the 8 lookup property names and the other table, 'Bridge Vis', has the 8 visibility states linked to the same 8 lookup property names.
A couple other gotchas on a block like this are to make sure the tables are set to 'Allow reverse lookup' and to make sure that the default position of the 'invisible' point, any moved linework and the default visibility state all correspond. That way you will avoid the 'Custom' option in the lookups.
