New EXIT MACRO action for clarity

[CRLF]

@tiffle

I've also noticed that each return action's parameter field can be left empty or not - nothing is passed back because there's nowhere to pass iy back to!

It looks like the do script command in the KM Engine AppleScript Suite would know the resullt, if it runs the macro--which is super--but otherwise it looks the exception. So on the side of safety, if you don't want do script to get the result, specify empty in the text field. To have it both ways, wrap the tell block in an ignoring application response.

ignoring application responses
tell application "Keyboard Maestro Engine"
do script "968B009A-A8F3-4554-839F-2B6B9BBA9CCC"
-- or: do script "return v cancel"
-- or: do script "968B009A-A8F3-4554-839F-2B6B9BBA9CCC" with parameter "Whatever"
end tell
end ignoring

WOW! When did this happen? Triggering a Macro from JXA can return a result!

Did you know that you can call a macro from JXA code, and have the macro return a value back to JXA? I swear this didn't used to work, but it does now. Consider this macro: [image]   And this JXA code: (() => { const kmEngine = Application("Keyboard Maestro Engine"); const result = kmEngine.doScript("My doScript Result Test Macro", { withParameter: "This is a test" }); console.log(result); })() Here's the console output: This is a test - Returned Mind. Blown. This is SO DAMN USEFUL!