It's good, Jim, but I'm not sure I agree that "Execute a Macro" doesn't qualify as a trigger.
The checkbox says "Triggered by any of the following". "Or by script" falls under the things that can "trigger" it. Like I said, just my opinion, but I don't think you need the part that says it's not a trigger.
But either way, I'm good. Thanks!!
devoy
September 16, 2019, 5:38pm
23
Got it, thanks Dan. I was thinking of the gear icon drop. Too early...
1 Like
Sleepy
September 16, 2019, 6:22pm
24
DanThomas:
It's good, Jim, but I'm not sure I agree that "Execute a Macro" doesn't qualify as a trigger.
The checkbox says "Triggered by any of the following". "Or by script" falls under the things that can "trigger" it. Like I said, just my opinion, but I don't think you need the part that says it's not a trigger.
I was tempted to make that very point myself, in my original post, but I wasn't sure I would win that argument. Thanks for saying it.
Dan, I understand your point. Logically, I also think of Execute a Macro as a type of trigger.
But, as I said:
Although Execute a Macro is not technically a trigger,
I still added it to the table of Trigger Types.
The very screenshot you provided does NOT have "Execute a Macro" as one of its triggers, and it is NOT a script.
The disclaimer needs to be there, because the table column title is:
Trigger Type
If it was NOT there, then some users might go looking in the Triggers popup list for "Execute a Macro".
IAC, I don't see the point. It is in the Trigger Types table, and that is all that matters from a clarity POV.
OK, I'm cool with either.