SAVE - v14 SAVE - v14
save {p,} {<file>} {,<message>}
or
save on|off {,<i>} {,<file> | *}
Function
Create a submodel from the current model.
or
Turn the autosave facility on or off. The facility enables the current model to be saved after a pre-defined number of modifications.
Parameters
|
p |
Implies that only the contents of the current model in the partition are to be stored. If p is omitted storage will consider items in the foreground. |
|
|
|
|
file |
The name of the submodel to be created. The default file extension is MOD. |
|
|
|
|
message |
A one line submodel description. If omitted, prompts for a description will be given: |
Prompt:
Description ?
{<message>}
As many lines of description may then be given. The last line should be terminated by a semi-colon or a blank line.
With no parameters implies that the submodel to be created is the submodel currently being updated (refer to the UPDATE command).
|
on |
Turn autosaving on. |
|
|
|
|
off |
Turn autosaving off. |
|
|
|
|
i |
The number of modifications after which an autosave is to be performed. If this parameter is omitted, the frequency will remain unchanged. The frequency at program startup is 25. |
|
|
|
|
file |
The name of the autosave file, the default extension is MOD. If this parameter is omitted and a previous autosave file name has not been defined, the name will be constructed from the current process-ID of the run, e.g. P1234MOD.MOD. An * instead of a file name will force such a name to be constructed if required. |
Examples
save
save valv100,’valve type a, length 100mm’
save p, tsofar,
save cw9x24
‘Clerestory Window, 900x2400’
‘Top-hung sash, Georgian wired glass’;
save on
save off
save on,piptemp
save on,25
Notes
When a submodel is created, all model items are stored, including those in invisible or untreatable fragments.
Submodel files are binary files and may therefore not transferable between certain machines of different manufacture. The commands A2MODEL and M2ASCII are available for this purpose.
If the classification coding facilities are active, then the classification code for the submodel maybe included at the beginning of the submodel description within parentheses. If it is omitted, the user will be prompted for a value.
At program startup, the autosave facility is OFF. If the autosave facility is on, a save will be made automatically before the commands RESET and KILL ALL.
Version Compatibility
[V12]When saving models remember V12 models may be not be read by any prior version i.e. 11.9, however V12 will read models and plot files from any version.
[v14 OCC] The standard SAVE command is enhanced allowing creation of a new model file that includes NURBS entities. This is implemented defining a file format that consist of the OCC-BREP file representing all the NURBS entities appended at the end of the standard model file that represent all the entities in the workspace. In particular this means that the definition of the Curve, Profiles, Surface, Shell and Body entities is split in two parts: their instance in the workspace, where each entity has its instance information (position and rotation matrix) and its attributes (color, pen, hatch and alphanumeric attributes), plus their inside definition, which is stored in the OCC-BREP section of the new Eagle model file, ready to be interpreted by OCC when the model is subsequently loaded.
The new Eagle version is capable of loading all previous Eagle model formats.
[v14] Version 14 model format can be read any previous versions of Eagle V.14 and V.12 unless the model file contains Nurbs entities, then, only starting from version V.12.6.0.B02, the V14 files with Nurbs can be read and loaded into the workspace however all the new entities will be skipped in V12.
See also