Handle References in the Drawing

Handle Design References

A drawing often has references to design elements. In order for Design Reuse to resolve those references at import the user needs to import the design elements first and then import the drawing. The drawing will be incomplete if this order is not followed, for example:

• ID-lists will have ADDE elements with unset references which means that "update design" will not work.

• Dimensions and labels referring to P-points and P-lines will have unset references.

There is no easy way to recover these references afterwards. Please import the design elements and the re-import the drawing.

In case the user copies a drawing between projects where the names of the design elements will change in the target project, design reuse will resolve most of the references. Some references cannot be handled automatically, for example: The criteria attribute in local representation rules. Design reuse will handle reference attributes where the attribute is of "reference type". In this case Design Reuse knows that this is a reference to an element in DABACON. If the attribute is just a text as in "criteria" design reuse will not do anything with this attribute value at import.

Handle Library and Font References

A drawing can have references to library element in the PADD database like backing sheet, symbol template, representation styles Design reuse cannot copy these element, they have to be properly setup in the target project before importing the drawings. The same is valid for true type fonts. The true type fonts used in a imported drawing must first be setup in the target project. Please note that fonts are referenced by name in the datal output: "FONT Arial" rather than "FONT 5". This means that the font numbers can be different in the source and the target project.

References to a Drawing

When importing a drawing that already exists in the target project, the old drawing element will be deleted and replaced with a new one. This of course, means that the reference number of the drawing is changed which will potentially break references to this drawing at import. However, Design Reuse will automatically try to reestablish some of these references. Currently Design Reuse will handle references from document links to the drawing.

Update Design/Update Anno

When importing a drawing the user may want it to automatically be recreated. Therefore there a to Design Reuse options: UpdateDesi and UpdateAnno. If the user sets them to "YES" the system will run "update design" and "update anno" at import. When this is done the system will open and close the drawings in the 2d canvas one by one as they are imported. If a drawing is open when import starts, the import will stop and the user will prompted if the open drawing is to saved.

Limitations/Known Issues

• True Type Fonts. Font attribute are set via the font name in the datal file in the transfer set. The font name depends on the operating system which can cause problems when transferring a drawing from a Korean operating system to an English operating system for instance.

• Getting Event Points in the Target Project. If the user opens an imported drawing in Marine Drafting and use the "Annotate/Label" function for instance, may find that Hull Drafting cannot find event points/p-points especially on outfitting models. To resolve this, the user must do an update design. (The explanation is that Design Reuse will not copy the picture file where Marine Drafting will look up some p-points/p-line information. The picture file is regenerated when the user updates design.)

• View Positions. If the user copies design models between projects with different GENTAB settings, imported hull panel will move to new position. If the user also copies drawings including those models and does an update design after import the models will move to a new position in the view. If it is as assembly drawing that normally have a 2d restriction with "clipping" activated, the models may appear outside the view limits and this means that they will disappear completely from the view. For Hull Symbolic Views, view planes given with frame terms or longitudinal positions will unfortunately not remain on the same GENTAB position after import. For example: if a hull symbolic view is defined on FR50 and FR50 means X=72000 in the source project, the view plane is still on X=72000 after import (which is another frame position in the target project).