Legacy Class/type orientation

<< Click to Display Table of Contents >>

Navigation:  Drawing Manager > Features and functions > Document codes > Document code implementations > Legacy drawing classes and drawing types >

Legacy Class/type orientation

Previous pageReturn to chapter overviewNext page

In cadett ELSA R32 and older, the Drawing Manager was much more limited than it is today. Then, you could have a "drawing class" and a "drawing type" to define the type of drawing sheet. The drawing type was seen as a sub-level of the drawing class.

 

Additionally, you could have one or two project related drawing types. If you had two, the second one was seen as a sub-level of the first. The project related drawing types were typically used to define plant and a location.

 

The use of drawing classes and drawing types is now only one possibility among many. The new generalised term "document codes" replaces the old "drawing classes", "drawing types" and "project related drawing types".

 

In old projects, and new projects created according to old settings, document codes from one or two trees are used. The first is called Class/type *LEGACY* and the second Proj. rel. types *LEGACY*.

 

An example of a drawing class could be "E for Electrical drawings". An example of a corresponding drawing type could be "K for Circuit diagrams". That could result in file names like EK___001.DXF and EK___002.DXF, where the first two letters of the file names specifies the drawing class and drawing type.

 

Legacy class/types like the one briefly discussed above are described in more detail in The "Class/types *LEGACY*" document code tree sub-topic.

 

Legacy project related drawing types, often used for plant and location, are discussed in the Example of legacy project oriented drawing types sub-topic.