Backward Compatibility
List of: Discussion Topic
Subjects: SAT Save and Restore
Contents: Kernel

The ACIS version number for subsequent save operations is set using the function set_save_file_version, which takes two arguments, a major version and a minor version.

Throughout the system, all entity save functions, and related functions for curve, surface, etc., take into account the version number. This is the global value, save_version_number, which gives the version of save file format being written. This can be used to produce a save file in a previous version's format.

Objects can be modified to be compatible with an earlier version. This may or may not result in loss of information. If the modification involves loss of information or a possible error in the resulting save file, a warning is generated, but the save file is still produced.

When restoring objects with shared subtypes, such as int_cur or spl_sur, from a save file in which they are not shared, the default is to share identical sub-objects rather than to leave them unshared.

Note The restore of pre-Release 1.6 save files causes the coedges in the entity restored to be ordered counterclockwise about their edge.

The version number is normally the current version, but the version may be set backwards to simulate save files generated by previous versions. A major version of 0 or less causes the version to default to the current ACIS version.

Set the save file version number:

void set_save_file_version(

int = 0,

// major version number

int = -1

// minor version number, default gives






// error unless major version is zero

);
PDF/KERN/10SAVE.PDF
HTM/DATA/KERN/KERN/10SAVE/0006.HTM