Basic use
One of the main differences between a single IMX file and a containerized IMX is that a single file can represent multiple situations. A containerized IMX, on the other hand, is a snapshot in time and can be seen as a single situation. For more information, refer to the way of working section
To maintain consistency and ease of use, the APIs for handling both single and containerized IMX files are designed to be as similar as possible. This allows end users to switch between single and containerized IMX files with minimal changes to their code.
Single file IMX
In this case, the IMX is a single XML file containing a situation or a project with an initial situation and optional a new situation. You need to define the situation of interest.
Containerized IMX
In this case, the IMX is a container holding multiple XML files that represent a snapshot in time. You do not need to define a situation.
The basic examples below can be switched using the tabs, making the differences clear.
todo: migrate to new tab ensure javascript tab syncer
Load file¶
Get file metadata¶
Get build exceptions¶
Query Objects¶
MultiContainer¶
Compair Objects¶
Below is a preview feature, changes will be made!