Block Attribute that Inserts a Separate Block

Block Attribute that Inserts a Separate Block

Anonymous
Not applicable
472 Views
2 Replies
Message 1 of 3

Block Attribute that Inserts a Separate Block

Anonymous
Not applicable

I'm wondering if there is a way to create a block attribute that could be tied to a Sheet Set Custom property to insert a block into said block?  I hope that is clear.  Basically, I'd like to modify our titleblocks for plan production to include an attribute that would insert the engineer's signature block based on the block name called out in Sheet Set custom properties.

 

I've done some googling and serached the forum and so far come up with nothing.  

 

Thanks!

 

0 Likes
473 Views
2 Replies
Replies (2)
Message 2 of 3

tcorey
Mentor
Mentor

I think this could be done programmatically without too much effort.

 

What I imagine I would do would be to create a block that has various visibility states, showing a different engineer's signature block for each.

 

Then, with AutoLISP, I would write code that reads the value of an attribute/field and flips the signature block to the correct visibility state based on that attribute value. Put the code in acaddoc.lsp or your Startup Suite so that it runs when you open a drawing.

 

An option if you don't like to program: If you know the name of the engineer before you create the sheet, just have a different template for each engineer and don't worry about tying it to an attribute value.

 

 



Tim Corey
MicroCAD Training and Consulting, Inc.
Redding, CA
Autodesk Platinum Reseller

New knowledge is the most valuable commodity on earth. -- Kurt Vonnegut
0 Likes
Message 3 of 3

Neilw_05
Mentor
Mentor

Should we assume your goal is to be able to change the signature block for an entire sheet set by changing the attribute in the Sheet Set Manager? Is it likely the engineer will change after the sheet set was created or will it be set once and only rarely need to change? If the latter I think Tim's idea of creating a seal block with multiple visibility states would be a simpler solution. The KISS (Keep It Simple Stupid) principle is usually preferred over customization when practical. Otherwise you may end up with problems if the customization fails or is not available to users downstream or in other domains.

Neil Wilson (a.k.a. neilw)
AEC Collection/C3D 2024, LDT 2004, Power Civil v8i SS1
WIN 10 64 PRO

http://www.sec-landmgt.com
0 Likes