It is hard to describe, so i will demonstrate two examples straightforwardly.
In the first example below, when created the action "macro run: this macro" in THIS macro, all the actions below the "macro run" action are cancelled. Or rather, the "macro run" action seems to block forever even if it is ended. In the example, the device will not vibrate eventually.
In the second example below, when created the action "macro run: recur bug" in ANOTHER macro and copied it into this macro, the recursion will function properly. In the example, the device will vibrate.
In addition, both of the "macro run" actions must check "block next actions until complete".
This bug can be quite bothersome, since you cannot create a macro run action with the current macro name, because there is only "this macro" to choose, which will eventually lead to a recursive bug. Therefore, i am really looking forward to the fixing of this bug.
In the first example below, when created the action "macro run: this macro" in THIS macro, all the actions below the "macro run" action are cancelled. Or rather, the "macro run" action seems to block forever even if it is ended. In the example, the device will not vibrate eventually.
In the second example below, when created the action "macro run: recur bug" in ANOTHER macro and copied it into this macro, the recursion will function properly. In the example, the device will vibrate.
In addition, both of the "macro run" actions must check "block next actions until complete".
This bug can be quite bothersome, since you cannot create a macro run action with the current macro name, because there is only "this macro" to choose, which will eventually lead to a recursive bug. Therefore, i am really looking forward to the fixing of this bug.