Description |
| Causes the Creo Parametric TOOLKIT program to spawn and connect to a new Creo Parametric session. It is intended for use in simple and full asynchronous modes. |
Synopsis |
#include <ProCore.h> |
ProError | ProEngineerStart | ( |
| char* proe_path | |
| /*
(In) |
| The path and file name of the Creo Parametric executable, or a script that runs it. For Creo+ use string "creoplus.exe " and set environment variable TK_ASYNC_CREO_AUTO_LOCATE=true This will auto locate Creo+ if installed and spawn it. Pass --profile --cwd as args to automate launch of Creo+ Pass arguments to Creo using token ++creo_tk For example, "creoplus.exe --profile profile1 ++creo_tk -g:no_graphics -i:rpc_input" Above value will launch Creo+ with profile profile1 and Creo will receive arguments -g:no_graphics -i:rpc_input |
| */ |
| char* prodev_text_path | |
| /*
(In) |
| The path under which the Creo Parametric TOOLKIT message and menu files are held. This is used in full asynchronous mode only. Otherwise, pass a null string. |
| */ |
) |
Returns |
|
PRO_TK_NO_ERROR | | Creo Parametric started successfully. |
PRO_TK_GENERAL_ERROR | | There was a general error. |
PRO_TK_NO_LICENSE | | Creo Parametric could not get a license to run. |
PRO_TK_APP_NO_LICENSE | | Creo Parametric was run without the licenses needed to run this application. |
PRO_TK_INVALID_DIR | | prodev_text_path is not a valid directory. |
other | | Error status returned by the application's user_initialize(). Special cases: - if the application is running in native mode instead of Unicode, PRO_TK_BAD_INPUTS may indicate that prodev_text_path could not be converted to or from Unicode.
- PRO_TK_APP_CREO_BARRED indicates that proe_path pointed to a Creo application that does not support Creo Parametric TOOLKIT.
|
|