Check if a parameter has been passed by "Execute Macro" or not

[Airy]

@henningaround

I want to be able to Execute a macro sometimes with a parameter passed, sometimes not.

I think I understand. The %TriggerValue% value is not "erased" when a macro is called. Indeed you are right, it can inherit its value from the PREVIOUS macro or mechanism that called it.

I think you will need to convert your macro to a subroutine trigger, and in that case you can determine what you want to determine, because then you can avoid this mechanism. I remember a long thread about this topic years ago.

Question about TriggerValue's meaning

Well, you're the Architect. Your word is final. I still love you. I don't object to most of how it works. What I'm mostly objecting to is the inability of a sub macro to figure out if the TriggerValue token was a parameter meant for it or if the value was meant for a parent macro. I also thought this part of the mechanism should be documented, and I even got Dan to agree with that idea. The wiki for TriggerValue doesn't explain this unusual behaviour at all. In fact the first line of the wiki…

Alternately, you can just check if the TriggerValue token "looks like" a hotkey or not.