Command: save

Syntax

save <file> {,<elist> ... }

Description

Save graphic entities in a disc file.

Parameters

• <file>
  The disc file to be created. If it already exists it will be overwritten. The default extension is .e.

• <elist>
  A group/entity list defining which entities are to be saved. If omitted, all entities are saved.

Switches

• -c
  If <file> exists request confirmation from the user before it is overwritten.

• -ef=<filter>
  A filter to be applied to all entities within <elist> further qualifying which entities are to be saved. If omitted, the filter current_filter is used.

• -gen
  Mark the file as having multi-generalized contents. This enables entities with different generalizations to be selectively rendered when the file gets instanced, see window.rank

• -lay
  Mark the file as being multi-layered. Typically a multi-layered entity file contains entities which are members of different external (non-global) groups. When such entity files are instanced (via the get command), then a window repaint redraws the instance for each layer rather than once for the window.

• -ll
  Convert all co-ordinate data to longitude/latitude before saving. The entity file will then be marked "long/lat". Conversion is done by applying the inverse of the current projection mapping. If mapping is currently defined, then this switch is applied automatically. Use -no_ll to suppress this behavior if required.

• -lug
  Record the lug status (entity.lugs) of entities in the file. If this switch is not present entity lugs cannot be shown when the entity file is retrieved.

• -o=<point>
  The point to be used as the graphic origin for entities in the file. If this is omitted, the global origin (0,0,0) is used.

• -t=<message>
  A description associated with the new file. If this is omitted, and <file> exists, then the description already associated with <file> will be retained.

• -tag
  Record the current values of all attach tags in the entity file for subsequent use as connector points. If omitted, tags are not recorded.

Notes

Sub-entities of compounds may not be saved in isolation from their parent entities. If this is attempted, the parent entity is also saved.

When entities are saved, their membership in groups is saved. However, only membership of groups which are in application atables is recorded. Membership of groups in the global atable (i.e. ~global) is lost.

Examples

Save one entity.

save my_model.e,this

Save all entities with change of origin, indicated interactively.

save layout, -o=pcur, -t=<'Rural Layout',current_date>

See Also