No this is not required, but in Full Asynchronous Mode, you should have created some callback Menus in Creo during you Init, after connection or after starting Creo.
In Asynchronous Mode, you should have an event loop, and call ProEventProcess.
If you call ProAsynchronousEventLoop the call may not return, until you don‘t interrupt this loop, the return may not needed if you have your own Menue Callbacks.
For PRO_COMM_MSG_EXE take care of blanks in the path, but if Creo is already started, this is probably not an issues any longer. You find the path after starting Creo and search for it in the Task Manager, just take this full path.
Please read carefully the notes in the TOOLKIT User Guide.
In Creo you have :
- Synchronous Mode (use the Creo Event Loop)
- Simple Asynchronous Mode (you need an event loop, if you need actions from time to time)
- Full Asynchronous Mode ( you have Menu Callbacks )
In Asynchronous Mode you may need ProEventProcess to push the execution of your calls. If you connect, do your task and disconnect, this may not required before each function call. Don’t forget you can run/connect to Creo on a complete other Workstation. But for sure you have the communication overhead.
