I see Debugger Breakpoint actions. How are these used?
I have a macro that is getting called inexplicably. How could I find out what is triggering it? I realize there are many possibilities and some are the kind I couldn’t catch, but maybe some kind of break point would help.
Add a Set Variable To action as the first action, and set it to the trigger info.
Then display this Variable, or view it in the KM Preferences.
That is deep. Ridiculous what’s in KM.
Would you please retitle this. It doesn’t really have anything to do with debugger breakpoints. I suggest “How to tell which macro called another?”