I have a macro that calls another macro. In the 2nd macro, I store off !MACRONAME. I was under the impression that this internal variable updated to the current macro, which is what it claims in the help docs.
When I echo it out though, it is showing the calling macro, not the current macro.
Is this intentional? And is there a way to get the current macro name?
Oh, good observations. As for a possible workaround, what is the reason why you need to know the macro name of the sub-macro?
I am creating a utility that tests several different executables by opening them, taking screenshots, and then closing them again. By setting the name of the macro to the name of the executable, then storing that name off, I can use a reusable macro that types the name of the executable provided, opens it, stores it off, and closes it again.
Each executable macro only contains 3 lines to store the name, echo it, and call the reusable macro so there’s very little redundant code and it makes maintenance and updates a lot easier.
It works amazingly well when I do each individual executable standalone, but when I try to create a overall calling macro to call all of the executables, I run into this issue.
I could just store off individual executable names in the the overall calling macro but that increases our tech debt and makes expanding the functionality more difficult.