Issue with visibility state of attribute blocks

[tomhY595S]

Hi I've created an Elevation block which has both attribute definitions for the view ports and visibility states for the different directions. Setup should be correct however when i test the block i am getting various attributes being visible or parts of the block visible when they shouldn't be (not corresponding to the changes I've made within the block editor) Please can someone take a look at the attached file to see what i'm missing? 

Thanks 

Tom 

[Libbya · Accepted solution]

Every attribute must have a unique tag.  You have (4) attributes with the same 'NUM' tag.  

[Libbya · Accepted solution]

Here's a more advanced way of implementing your block, but the end result is far more friendly to use than sifting through a text list of visibility state names for the one you want. See screencast.

[tomhY595S]

WOW. That is super impressive. I didn't even realise that was possible. 

Thanks very much. Will need to study the lookup table further looks like a powerful tool 

Best

Tom

[tomhY595S]

Hi Libbya, 

Just tried this out. but seems mine isnt't working the only difference I can see is with the visibility lookup of the 2nd table. When you added your lookup table. 2 appeared. when I did mine only 1. so made a 2nd. thefore it shows as lookup 2 but within it when add properties it changes to table 3. - Would this have any impact? 

Additionally just to check the flip command is  the regular flip action? 1. select flip state then the visibility lookup? Attached my block. also the 2 screenshots of the lookup tables

Thanks 

Tom

[Libbya]

You need to use a Double Lookup.  

https://forums.autodesk.com/t5/dynamic-blocks-forum/how-to-make-a-double-lookup/m-p/5785708

[Libbya]

The flip parameters and flip actions are ordinary.  I add the visibility parameter to the flip actions because the flip actions need something added to them in order for the flip grips to appear when the block is inserted.  The visibility parameter is just a convenient object to add to the flips because it is invisible when the grip is removed and it doesn't matter where it is located or whether or not it is flipped.  

[tomhY595S]

Thanks again for this, so the function of the BACTIONBARMODE is to allow editing of the tool pallets. I've added it to my own pallet. However, the issue I now face is that the properties window in Autocad 2021 is significantly different to the 2015 one you've shown in that video. I cannot find the same option to duplicate the lookup in the same way. Please see the screenshot. can you please pin-point me to the same thing in version 2021 or similar?

also added screenshot of the one from 2015 

Thanks 

Tom

 

[Libbya]

You start from the PARAMETERS tab of the block authoring palettes.

Copy the Lookup PARAMETER.

Paste a copy.

Right click and select properties of the new tool.

Change the name.

Add TWO lookup ACTIONS to the lookup PARAMETER.

Exit properties.

See screencast.

[Libbya]

Also, BACTIONBARMODE = 0 just changes the display of the actions (and allows actions to be added to the selection sets of other actions).  The change in display allows you to see and select either of the two lookup actions that are associated with a single lookup parameter.

[tomhY595S]

Hey, Sorry i'm still having issues with the double lookup. I've managed to re-create as you have but when I do only one box is displayed not two. - https://share.getcloudapp.com/04uQPqzG 

I've attached the block. too 

Is this block only possible with the double lookup? 

Thanks 

Tom

[Libbya]

In your video, you have BACTIONBARMODE = 1.  Because of that, you cannot see both lookup tables.  Set BACTIONBARMODE = 0 and try again.  When I open your block and set BACTIONBARMODE = 0, I can see FOUR unused lookup actions!

[tomhY595S]

Hi Libbya, 

Hope all is well. I've managed to do it this time, though I'm still getting some issues with both the visibility of attribute texts showing when the arrow is not and the flip not working smoothly. please see screencast - https://share.getcloudapp.com/4gurjrGO 

and attached block. 

Can you see where it is that I've gone wrong?

Best

Tom

[Libbya]

I think that the issues are from two things.  First, after making changes to an attribute definition, you need to run attsync.  That clears up the attribute/visibility discrepancies.  The second issue seems like it is just a matter of coordinating the numbering of the flip parameters, the visibility names, and the items that are visible in those named states.  Given the attribute numbers of 1-4, it seems sensible to have the flips numbered in the same way, and have the visibility state names represented in the same order.  Given that the 1-1-1-1 state is all on, it follows that 1 is ON and 0 is off.  Therefore a state name of 0-1-1-0 would have flip/att 1 OFF, flip 2/att ON, flip/att 3 ON, flip/att 4 OFF.  Hopefully that makes sense.  Once those are coordinated properly the block works fine.  See screencast.

[tomhY595S]

Thank you very much for that video, Learned a lot more about the process of why the settings were the way they were. So I've replicated as you've got it and double-checked the terms logically. applied the art sync and fixed the flip as you've had them. It works mostly when you flip in a certain order, and in other orders, it reacts unpredictably. can you see if this also is the case for your block? see screencast. I assume the issue now is there is likely a flip state that's associated incorrectly? - https://share.getcloudapp.com/2NumyX1G 

[Libbya · Accepted solution]

At that point it is a process of diagnosing the individual states.  Primary causes would be errors within the visibility state, errors on the input table (with the definitions of the flip states), or errors in row names on either table (row names must match EXACTLY).