This section explains about configuring the 3D Image path for a type.
The fourth and fifth properties together define the navigation path,
format to fetch the CGR file (3D image file) associated to the object of
that type. Navigation path is basically, matrix path to reach the object
that contains the CGR file that corresponds to the object at which we are looking.
The value of this property (i.e. ImagePaths
) can be a comma-separated string, in which each token is a navigation path to get the CGR
file for the object type. System will search for CGR files starting from
the first token, until it finds a CGR file till the last token. As soon
as it finds a CGR file, it will ignore the rest of the navigation paths
defined in this property.
For example:
3DLive.ImagePaths.Engineering_Central.type_Part =
$<to[relationship_ImageHolder].from.id>,\ $<from[relationship_PartSpecification].to.id>
The above property tells the system to get the CGR file for any object
of the Part type by navigating the paths defined above. In other words, first try with
the path "$<to[relationship_ImageHolder].from.id>
. If it is not found,
try with the path “$<from[relationship_PartSpecification].to.id>
).
Note:
For each navigation path defined in the above property (i.e. ImagePaths
), there MUST be a corresponding format defined in the
fifth property (i.e. ImageFormats
).
The above two properties go together. System uses the path defined in the
fourth property (i.e. ImagePaths
) to reach the object. First
system will split the value of this property into various distinct paths
based on the comma separator. System will try to find an object for each
of these tokens (each token is navigation path) until finds an object. Once
an object is found for a path, then it uses the corresponding format to
see if a file exists in it. If the file does not exist, system will continue
its search for CGR file using the next navigation path defined in the
ImagePaths
property. If it finds one CGR file at any point
during this operation, it will return the file, and stop looking further.
If it does not find a CGR using any of the paths defined, the client will display
a default image to the user.
Note:
There is one-to-one mapping between the navigation path and
formats (i.e. ImagePaths, ImageFormats
). If the first property
defines five navigation paths, there must be five formats defined in the
second property.
The system maps the first path to the first format, the second path to the second, etc.