Damon Bell
Correction on my response…
It appears that you do need to use await for the invokeCommand to prevent your plugin from processing any more lines of code until EZGS is done. When I tested last night, it seemed that wasn’t needed but today it is, really strange.
Anyway, it doesn’t hurt anything to use await so to be safe you should just always use await before invokeCommand to ensure it will wait for EZ green Screen. So your batching plugin needs await before the invokeCommand. Also EZ Green Screen also needed await in the entrypoints setup command function to prevent it from telling your plugin it was done before it was….. what a pain.
await plugin.invokeCommand("ezgsCommand");
So use the command like shown above and make sure to use the EZ green Screen CCX labeled test-2. Please let me know if that works.
-
This reply was modified 3 months, 1 week ago by
Damon Bell.
-
This reply was modified 3 months, 1 week ago by