Intellegent Dynamic Block

[Darren Allen]

I have attached a block that I have created with four different visibilty states. It works well while testing and it shows that it is dynamic when selecting to edit (Lightning Bolt) but will not show dynamic when selecting to insert or act dynamic when inserted into a drawing. What am I doing wrong? Please advise, Thanks!

[edwinprakoso]

I have attached a block that I have created with four different visibilty states. It works well while testing and it shows that it is dynamic when selecting to edit (Lightning Bolt) but will not show dynamic when selecting to insert or act dynamic when inserted into a drawing. What am I doing wrong? Please advise, Thanks!

It works at my end. But I'm confused, how did you created the block? Because I see warning your file has authoring elements. Aren't the elements supposed to be in a block, not in a DWG file?
I tried to insert 1_Inverter_Base_A and the visibility states work just fine.

[clshade]

First it is Dynamic.
The Vis Parameter is off in the distance when you insert it
Zoom out while the Block is highlighted and you will see the Parameter.
Sometimes a couple of trips through WBLOCK will bring it all together.
This happens typically when the entities for the block are created somewhere away from 0,0 or when a bit of geometry is made into a block and then Dynamic Properties are applied to it.

As for the other posters question: The Dynamic Properties are with the Block when it has been inserted. With the advent of the Block Editor most who create a DynBlk are no longer saving the Block within the container file. The warning is there to let the user know that this Drawing File has Dynamic Properties so that the casual user is less likely to change the entities and therefore change the Dynamic Properties of the block.
Been happening for years.

[Darren Allen]

Thank you for clearing up the note wawrning I get everytime I open a file. I will no longer be concerned.

I did notice the Visibility Par would be completely off the mark while coming back to Block editor. Didn't realize this is what has been making it appear to be dynamic. Thanks for clearing that up as well.

[Darren Allen]

I have yet another Dynamic block I am having issues with; it is suppose to flip up or down, and it does, however, some of the attributed text will not flip with it as well as the top attribute does not appear in the drawing. Please see attached and advise, Thanks.

I will edit this post later to uplaod the file. The uploader will not upload for me right now.

The system is not letting me upload any files. It begins pulling the file from its location and then stops and gives the 302 error event. I will upload as soon as I can. Can the older files that are of no use be deleted from the FUM? How?

Any other help or advice as to why I loose att. text or why the att. text will not flip (without an uploaded file) will be greatly appreciated. Thanks!

[clshade]

Two common problems:
Attribs in DynBlk's must be Locked.
Each Attrib must have a unique TAG.

Either issue with yours?

[Darren Allen]

Two common problems:
Attribs in DynBlk's must be Locked.
Each Attrib must have a unique TAG.

Either issue with yours?

Attributes now have unique tags, how do I "Lock" them...with constraints?

Finally able to upload. Please review and advise, Thanks

[clshade]

That I don't know as I do not have access to Constraints or knowledge in their use.
What is the Constraint need on this block?

Also, sometimes when mucking with Attribs as you have you may need to delete and recreate the Attribs.
They will get "hung" from time to time.

[Darren Allen]

Constraints are a form of Locking an objet(s) to a specific location base on specific parameters. It can be parametric in that the constrained object will move in relation the position or object it was constrained to, if those objects move. I have tried this with this block and it does not work in this situation. How did you mean to lock them? Thanks

[clshade]

Attributes, since the introduction of Dynamic Blocks, have had an additional parameter along with Invisible, Constant, Verify, named Lock Position.
When creating a new DynBlk with Attrib's this is checked by default as Attrib's are required to be Locked in DynBlk's.
Older Blocks that are having Dynamic Properties added to them will need to have this parameter checked in order for the Attrib's to behave.
Often though it is easier to erase and recreate the Attrib's for the DynBlk as I have found them to still be hinky when doing this with older Blocks.