- Concerning knowledge patterns and power copies, copied objects can be retrieved
using
GetAttributeObject. For example, when
instantiating a power copy using the
InstantiateTemplate function, copied objects can be
retrieved using the object
returned by InstantiateTemplate.
The expected name is the name used when defining the power copy. - The size of the knowledge pattern lists evolves during the execution of the pattern as if it had never been executed. It is possible to add items to the list in a different order than the normal one i.e. you can begin with the second item, then create the first one. But if items are missing at the end of the execution, the list is "compacted". Some indexes are changed, and a warning message appears.
- There is an automatic naming strategy of instances, but this naming strategy can be overloaded through attributes found on instances (Name attribute for both user objects and datums). Mandatory attributes are required to ensure the complete instantiation of a 3D template. If an error occurs during the knowledge pattern execution, or if not all these attributes are filled, the instance is removed, even if it was already and correctly generated.
- The re-execution of the knowledge pattern does not load the template documents if the resource table identifier is not modified. The application does not check if you modified the user object reference before you re-instantiate it.
|