Hello all,
There is no need to add macros to config.pro.
What this article is telling us is to make two UI commands. (UICreateCommand in C++ OTK)
The first UI command (which starts the whole process) should be placed on the ribbon for a user to click...
The first UI command does whatever it has to do and in the end calls some macro string which does what you need this macro to accomplish with a user doing something interactively...
This macro string in its last statement has to call the second UI command, something like this:
mapkey(continued) ~ Command `UI2`;
The second UI command, after it would be called by the first macro ,would have a control over pro/e session, again.
The event loop per this article goes like this:
1. a user interactively calls the 'ribbon-shown' command.
2. OTK gets control over pro/e session and does some work.
3 OTK calls a macro at the end of its run.
4. Control returns back to pro/e, macro executes, possible interactive user actions.
5. the macro calls command#2-click at the end of its run.
6. OTK starts execution of command #2 with the control back to OTK.
HIH.
FV.