- Posted on
Fri Oct 18, 2019 11:17 am
-
matt (support)
offline
- Site Admin
-
- Posts: 21416
- Joined: Jan 27, 2003
- Location: Texas
-
Action executing in Indigo, especially via APIs, is a very asynchronous operation. Plugins and scripts run in their own processes, and actions in an Action Group can call out to other plugins (or execute scripts, etc.), not to mention multiple threads in the Indigo Server and potentially plugins. Trying to have everything wait/block is a good recipe for lots of deadlocks to occur, so in-general the blocking needs to occur at the most atomic level possible (in this case the execution of individual actions in an Action Group). So while I agree with you from a simplicity of API perspective, from an architectural level it isn't something we are going to do.
You can leave in actions that execute external AppleScript files, but Indigo has (and continues to) spin up a new process to execute those. So I'm not sure that will address the problem you are having.