Table lookup not seeing correct values

Table lookup not seeing correct values

timothy_crouse
Collaborator Collaborator
649 Views
7 Replies
Message 1 of 8

Table lookup not seeing correct values

timothy_crouse
Collaborator
Collaborator

Can someone look at this block and explain to me why the lookup table keeps reverting to a custom selection.

 

Although the header reverts to a custom selection the width is set correctly to match up with the row block.

 

If I delete teh lookup table and reinsert it that instance of the block sees the correct values in the lookup table which then allows the selection to match a predefined section.    But if you save it out then re-insert it (the header block) the custom selection re-appears in the selection list.

 

 

Thanks in advance

Tim C.

0 Likes
Accepted solutions (1)
650 Views
7 Replies
Replies (7)
Message 2 of 8

Libbya
Mentor
Mentor
Accepted solution

Your as-drawn value for header width parameter does not match the value in the lookup table.  You don't see the discrepancy because your precision (luprec system variable) is too low.    

 

 

0 Likes
Message 3 of 8

timothy_crouse
Collaborator
Collaborator

how did you get the abandoned lookup tables to appear?  I do not see them on my machine.

0 Likes
Message 4 of 8

Libbya
Mentor
Mentor

Sys variable BACTIONBARMODE=0.  It is also useful for seeing both tables of a double lookup or adding one action to the selection set of another action.  It can cause issues if you aren't familiar with the results, though.  

0 Likes
Message 5 of 8

timothy_crouse
Collaborator
Collaborator

 

 

One more time please......

 

I set my units to 0.000

 

I verified that the linear move list items were 3 digits

 

I verified the table columns are set to the 3 digit values

 

But custom still appears in the selection choice.

 

0 Likes
Message 6 of 8

timothy_crouse
Collaborator
Collaborator

I think it click'ed

 

I noticed the overlapping of the lines at a tight resolution

0 Likes
Message 7 of 8

Libbya
Mentor
Mentor

The ACTUAL length of the parameter needs to match the value on the lookup table.  Changing the precision does not change the as-drawn distances, it just changes how precise your perception of them is.  If all you did was change the units and change the precision then you did nothing to change the as-drawn distance of the parameter and so it STILL does not match the value in the lookup table.  There are various two ways to fix it, either change the as-drawn default value of the parameter or change the lookup value.  I changed the lookup value in the last screencast.  I'll change the as-drawn parameter length in this one.  I would recommend ALWAYS setting the precision to the highest value (luprec=8) so that you can always see any discrepancies.  i would also recommend being more precise when drawing to avoid those issues in the future.  See screencast.  

 

 

0 Likes
Message 8 of 8

timothy_crouse
Collaborator
Collaborator

Thank You

0 Likes