Wow, this works for me
I've just made 3 macro's for testing and runs pefectly (for now
) without any variables
View attachment 1592View attachment 1593
View attachment 1594
Thx guys
It's ok if you don't need any return values
Either you need or not, the colled macro works as "semi-parallel" executable subroutine.
Once you call the function-ish macro, by Run macro action, it starts proceeding immediately, and progress till a statement which has the context to wait, cancel or finish. On the breaking time, MD main process switches the current executive target back to caller macro(or 3rd, 4th... macros).
So it doesn't guarantee it finished what you want to do in the subroutine. In some cases, you can't avoid to place wait actions before you get the final result of the subroutine, i.e. it contains UI interaction, replace_all to long text, too many loops or so. You need to mind their dependency carefully while running semi-asynchronously when you didn't ticked Wait to complete... option. It might cause an unexpected behavior.