|
The history manager allows the user to roll directly to a named state even if it is across multiple branches. It is possible to cycle through all branches of the history within a single stream.
|
|
|
The history manager supports multiple history streams. As you create and work with different parts, the individual parts maintain their own independent history streams. As an example, when working in Scheme, parts are managed in independent windows.
|
|
|
The history stream maintains three pointers. The first pointer is to the root delta state. The second pointer is to the last noted active delta state. The third pointer is to the delta state currently being created.
|
|
|
|
|
Figure 7-7. History Stream Structure
|
|
|
The following functions may be used with or without the
Part Management Component.
|
|
|
Memory Management:
|
|
|
api_prune_history
|
Remove delta states in a history stream
|
|
|
Save/Restore:
|
|
|
api_save_entity_list_with_history
|
Save history information with the part
|
|
|
api_save_entity_list_with_history_file
|
Save history information with the part
|
|
|
api_restore_entity_list_with_history
|
Restore the part and history
|
|
|
api_restore_entity_list_with_history_file
|
Restore the part and history
|