If you drop one of those into the plan, do you really always want to get the "Blah blah layer is not displayed. Maybe it would help to look at some blatantly obvious examples of generic CAD blocks that could be used in any number of different views like a Break Line or a Graphic Scale. I can't speak for Chief, but I believe it was absolutely intentional, and I think they made the right call. I'd love to know if there's a reason Chief does this I'd love to know if there's a reason Chief does this, or if this is an 'unplanned' behavior. Currently Chief is undoing the 'override', right? If I want it to stay on the current cad layer, I don't need to take any further action. But if I intentionally want it on an assigned layer, and go through the process of doing just that, why does Chief undo that as the block slips into the shelves of the library?
Cad blocks chief architect library manual#
If we're picking one or the other, I think the current dynamic behavior is just a lot more valuable than the suggested static behavior.īut Michael, I'm not suggesting a static behavior, but rather a manual override that allows my intentional control. If the program simply used the original layer that would remove a lot of the robust control we have otherwise.
![cad blocks chief architect library cad blocks chief architect library](https://ceco.net/autocad-download/free-drawings-dwg-dxf/autocad-drawing-smith-house-exterior-perspective-one-richard-meier-architect-architecture-dwg-dxf-452.png)
![cad blocks chief architect library cad blocks chief architect library](https://149512171.v2.pressablecdn.com/wp-content/uploads/2019/09/cad-03-17.jpg)
I think it works really well having CAD blocks placed onto the Current CAD Layer regardless of the original layer. What I'm saying is that I don't agree that the layer should "stick" when storing in and pulling from the library.