Default Visibility State

[sovby254640]

We have a block library drawing that every one copies from into their project. It consist of a mixture of dynamic blocks, traditional blocks & various other linework & notes. When somebody copy clips out of that file & into another file the dynamic block comes in as whatever the default visibility state is. Is there a variable that i can set where whatever state i have a block set at it will remain the same when i copy it into another drawing?

[clshade]

I do not think so.
The question I have is why would you want the DynBlk to be static? The whole idea of DynBlk's is that they can be changed.
Are you all looking for the one block that is already the "right" block? If so, why did you create DynBlk's to begin with?
Palettes may be a better way to get the DynBlk's you need quickly

[sovby254640]

We have one drawing file that we use as a template. It is made up of a combination of dynamic blocks, regular blocks, & just varoius linework items. My library has for instance wall sections that are made up with multiple dynamic blocks. I might have one that has a 2x6 stud wall, a window, a header, etc. In my stud wall dynamic block if the default visibility state is a 2x4 stud wall when i copy it into the project the visibility state changes to that visibility state no matter what i have it set to in my section. When i refer to default i mean the one that is at the top of the list. I am using tool palettes for alot of our individual blocks but i do not want to have to build the section every single time. What we do is take the section that i have set up & copy it into a new project.

[StDoodle]

Yeah, blocks are always going to default to their defaults when brought in for the first time; keep in mind that what you bring in is an instance of the block, not a copy of the existing instance. Palettes are usually the best way, IMO, to pre-set some of the dynamic block properties, but it sounds like you have a large number of dynamic blocks that make up one "detail" that you want to bring in all at once? I think, but I'm not sure, that your best bet might be to make each of the collections-as-details of dynamic blocks into a static block, with the inside / nested dynamic blocks set to the "proper" settings. I believe that if you bring in that block and explode it, it will leave the dynamic blocks set as you desire. Maybe.

Edit to add: if this works, you can even put each of your "detail collection blocks" into a tool palette, and set them to auto-explode upon insertion, which should give you, in practice, exactly what you're looking for; albeit in an "odd" way.

[clshade]

OOTB thinking there!
;)