This is documentation of an archived release.
For documentation on the current version, please check Knowledge Base.

Orbit Object List

  • Gather a list of objects: Either in the Object Inspector, The Find Objects Tool or The Query Objects Tool.
  • Open the Open & Save Operations dropdown list:
  • Object List files (*.ool: Orbit Object List) do not store objects, but only their references: the identification of dataset, model and object (ID's). When opening an object list, the user must take care that the required datasets are available.
  • Object lists would best be used for temporary use only since you might loose exact object references when modifying the data: e.g. when deleting objects and saving the modified dataset, the object ID's might be different next time you open it, as some storage formats cannot withhold an object ID.
  • Since the Object Inspector and its tools are reused in several tools (e.g. Find and Query results), the object list is a very useful tool for temporary storage. Using the list-comparison and merging tools in e.g. the Find and Query windows, it is possible to compare the object lists that were prepared earlier and make new lists or datasets from there on.

The Orbit Object List (.ool) is a file that contains a set of objects. This set of objects can consist of objects from different models and even different datasets.
An .ool file bundles your choice of objects into a single file for easy and fast recovery.
The Orbit Object List can be created in three ways:

The .ool file is only supported by these 3 functions.
It can be created, opened, saved and saved as another filename in the Open & Save Operations.
The Open & Save Operations are the same for all 3 functions, only the gathering of the objects is different (by selection, by searching or by querying).


(*.ool: Orbit Object List) do not store objects, but only their references: the identification of dataset, model and object (ID's). When opening an object list, the user must take care that the required datasets are available.

Object lists would best be used for temporary use only since you might loose exact object references when modifying the data: e.g. when deleting objects and saving the modified dataset, the object ID's might be different next time you open it, as some storage formats cannot withhold an object ID.

Since the Object Inspector and its tools are reused in several tools (e.g. Find and Query results), the object list is a very useful tool for temporary storage. Using the list-comparison and merging tools in e.g. the Find and Query windows, it is possible to compare the object lists that were prepared earlier and make new lists or datasets from there on.

 
Last modified:: 2019/03/25 11:36