Differences

This shows you the differences between two versions of the page.

--- action:Debugger_Start [2015/07/06 07:48] – created peternlewis
+++ action:Debugger_Start [2026/04/23 03:32] (current) – [Using the Debugger] peternlewis
@@ Line 1: / Line 1: @@
+====== Macro Debugger ======
 Keyboard Maestro includes a built-in macro debugger which you can turn on by choosing Start Debugging from the Status Menu, or by using one of the various Debugger actions.
-The Debugger actions include:
+{{ manual:macrodebugger.png?nolink&683 |Macro Debugger}}
+===== Debugger Actions =====
 * Debugger Start.
@@ Line 17: / Line 23: @@
 * Debugger Continue All Macros.
-If a macro is paused, or if a macro starts paused, but the next action is a Debugger action, it will run anyway.  This allows you to to create macros with hot keys and Debugger actions to breakpoint, step through, continue, etc other macros without themselves being debugged.
+===== Using the Debugger =====
+If a macro is paused by the debugger, or if a macro starts paused, but the next action is a Debugger action, it will run anyway.  This allows you to to create macros with hot keys and Debugger actions to breakpoint, step through, continue, etc other macros without themselves being debugged.
 Keep in mind that once a macro has started executing, the engine has taken a copy of the macro to execute, so any changes you make in the editor will not affect the execution of the macro (although any changes you make to a sub macro that has not yet started executing would apply).
-Also keep in mind that macros can often be time sensitive, so if you find your macro runs fine when stepped through in the debugger, but not when run normally, the issue is probably that the macro is executing actions like click actions before the system has caught up and the screen is stable.  Add an appropriate Pause action if that is the case.
+Also keep in mind that macros can often be time sensitive, so if you find your macro runs fine when stepped through in the debugger, but not when run normally, the issue is probably that the macro is executing actions like click actions before the system has caught up and the screen is stable.  Add an appropriate [[action:Pause|Pause]] action if that is the case.
 If you close the debugger window, the paused macros will resume their normal operation.
+===== See Also =====
+  * [[manual:Macro_Debugger|Macro Debugger]] user manual section