2010-09-28 06:54 PM - last edited on 2023-05-25 05:33 PM by Rubia Torres
2010-09-28 09:30 PM
2010-09-28 10:53 PM
2010-09-29 05:31 AM
2010-09-29 12:28 PM
2010-09-29 02:46 PM
fuzzytnth3 wrote:I think almost any item on Layouts are an exception to this. (Exception that proves the rule? )
1
Never leave anything on the ArchiCAD or Zero layer.
2010-09-29 11:31 PM
David wrote:Agreed.fuzzytnth3 wrote:I think almost any item on Layouts are an exception to this. (Exception that proves the rule? )
1
Never leave anything on the ArchiCAD or Zero layer.
David
2010-09-30 01:15 AM
Matthew wrote:Not here I'm afraid. Layers may be as useful in the layout book as they are in the modeling environment. All of our drawings go on a DRAWINGS.L layer, titleblock info on a TITLEBLOCK.L layer, amendments on an AMENDMENTS.L layer, etc. All of these layers can be used to show different layout setups.David wrote:Agreed.fuzzytnth3 wrote:I think almost any item on Layouts are an exception to this. (Exception that proves the rule? )
1
Never leave anything on the ArchiCAD or Zero layer.
David
2010-09-30 11:30 AM
2010-10-03 09:25 PM
Erwin wrote:Yes. This is important. I always set up clear naming conventions for company standard attributes (which are to remain unchanged) and project specific ones which obviously may be freely adapted to the needs of the project.
Don't alter attributes that are part of (company) template, to ensure that copy/paste between different projects based on the same template give proper results. For example altering a material to have a different coverfill. Instead make a new material.
ArchiCAD specific, but one I feel is quite important if you're in the habit of re-using bits of old work.