I have not been able to find anything in the doc or forum that explains what the macro controls "Step Over", "Step Into", and "Step Out" do. Step over, into, or out of what? The macro? What would that do?
But what does any of that DO? You are answering my question with the same terms that I am asking to be defined. I'm sure it will all make sense when I finally understand it, but it's a foreign language at this point.
What IS "stepping over an action"? What am I "stepping over" and where do I go from where I am? How does any of that apply to "If Then" actions and Groups?
Does it skip the actions, or execute through them until the next debugging interruption to make a similar decision?
I have a linear sequence of actions. What does it mean to "step out of" the current current action? If there is only a linear sequence, with no loops or branches, does "stepping out of" the action exit the entire macro?
What does it mean to "step into" an action? Presumably the actions, groups, branches, loops, whatever, are being executed in the way that they are written to be executed. Where is INTO? Into what?
I appear to be missing key concepts of what the Debugger is actually doing and how I interact with it and I cannot find explanations anywhere. It took me 20 minutes of searching just to find names for what the buttons are, but the names are no help. It would be lovely if there was a tutorial, but I haven't found it yet.
There is a complete disconnect between the macro shown in the editor and the macro run in the engine, so this sort of close integration is impossible without a completely different design to Keyboard Maestro.