A Toolkit application or Object Toolkit application could benefit from being able to read from the trail file during or after a Creo session.
One possibility that comes to mind is to read more detailed error descriptions for problems for which the API just returns the general PRO_TK_GENERAL_ERROR.
For example trying to open a DRW with missing dependencies or opening a file created by an educational version of Creo in a commercial version of Creo.
In both cases PRO_TK_GENERAL_ERROR is returned, but an application cannot tell the difference between the two error cases.
This is particularly relevant when running Creo in hidden batch mode.
The name of the Creo trail file is "trail.txt.[n]".
Request: provide an API to get hold of the current trail file name.
Other users interested in this functionality:
Pro/Toolkit access to audit trail information
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.