After further investigation, I noticed that the node ID through RetrieveNodeInfo is likely a sort of memory address. If it is memory address, the IDs might be valid only within a session.
What I'd like to do is to save/load node status outside of .vds file. Each node should be manipulated independently, so each node should be distinguished and operated by unique identifier.
Through SAP 3D Visual Enterprise applications SDK (I assume version 2.4 should come soon, but I'm using 2.3 now), accessible IDs via RetrieveNodeInfo are node ID, NodeName, AssetID, UniqueID. The SDK provides 3 ways to manipulate nodes, API, Query Language and Paint XML. I've used API with node ID to manipulate nodes, but I have to use alternatives (Query Language or Paint XML) since node ID is unlikely persistent.
I'd expect AssetID or UniqueID for the purpose. But those IDs are often empty, and it is not clear which variables in Query Language are assigned to the IDs.
I've concluded the issue as the following slide.
Solutions might be:
- To assign unique AssetID/UniqueID to each node by VE Generator automatically.
- How to do it?
- Still need to know how to use the ID with API, Query Language or Paint XML.
- To make NodeName unique.
- Is it possible to assign unique names automatically by VE Generator?
- Mapping between unique NodeName and actual name should be provided in independent file, which should be generated by VE Generator. How to do it?
I really appreciate your comment.
Thanks in advance,
Shinya