Double Lookup + Point + Move

[NF_Sam_R]

Normally a lurker so this is my first post, but there's something I just can't figure out after scouring every possible forum post I can find about it, and I'm unsure if I'm making it far more difficult than necessary for myself. The basic aesthetics of the blocks are totally fine, and the top block in the attached document has the double lookup and visibility states working as intended.

The part where I'm running into problems is when I'm trying to have that double lookup assign the location of points that would have equal vertical justification depending on how many attributes are shown. E.g. A ratio of 1:2 (1 cable note, 2 key notes) would have the box with 1 attribute would be vertically centered in the visible area.

Within the digging I did, I saw mention of using point parameters and their X/Y coords with the double lookup tables, but I'm unsure how to integrate this into a double lookup table like this, especially because I have 25 visibility states to allow anything from 1&1 to 5&5. To list off what I'd say my "simple" questions are:
- When referencing a Point Parameter in a lookup table, do you need to reference both the X and Y coords, or can you just reference one of the two if only one of the two will ever be changing inside the block?

- Would the default point coords at every possible viewport be entered in the input properties of each individual lookup so they can be referenced in the double lookup table, or can the double lookup go back and assign those coords without them being initially defined in the individual lookups?

I have the full list of positions that each point would need to end up in per visibility state in the bottom version of the block that isn't working, I just an unsure how to get that data into a manner that the double lookup works as intended.

If there are any questions, please let me know! (I'm also aware this is arguably making things far more difficult, but this will be used for every single drawing by my team, so I think it's worth the initial frustration on my end.)

[h_s_walker · Accepted solution]

@NF_Sam_R I think I know what the problem is. Unfortunately it means more work for you.

On a side note the good news is you don't need to use the move X values only the Y values need to be used.

Now onto the problem. You've got all your Cable and Key move properties in the wrong lookup table.

In Cable and KeyNote you only need Number of Cables and Number of Keynotes. 

In Visibility lookup you need Cable Point 1 to 5 and Key Point 1 to 5 (but only the y values).

When you sort that out your block should work as intended

EDIT: See the attached drawing. Your block is now working as you wanted it to

[NF_Sam_R]

That was exactly it! This was my first time dabbling in double lookup tables that actually moved a set of points that weren't always visible. Much appreciated!