Tip:
Highlight text to annotate it
X
The Job Designer also doubles as a debugger
each and every time we run a job through it.
This is very useful for checking that our Job runs as it should
and eliminate errors.
When we run a job from within the Designer,
it actually runs in Debug mode.
This means that there’s a small delay introduced before each action,
enough to allow the user to visually follow the sequence of execution.
While the job is running
we can observe the variables change.
However,
in some cases, we may need to pause the Job to get a closer look of the current results.
For that,
we can use a break point to pause the execution of a job, whenever needed,
by selecting the action
and choosing from the Debug menu
the Set Break Point option,
or by simply clicking on the empty space (in the grey area)
to the left of the action.
As a result,
the running job will pause when it reaches the break point
allowing us to examine the variables
and any other aspect of our system.
Having done that
we can now either click on the “Start” button to resume,
or click on the “Execute Next Action” button
to go through our job one action at a time.
We are also given the option of starting our job from a specific action,
by right clicking on it,
and selecting the “Start from Here” option in the context menu.
Within the Job Designer Options,
found in the tools menu,
we can configure the Debugger to run the Jobs according to our needs.
Here we can specify the delay between the actions,
with the default being 100 milliseconds.
Note that while this may seem minimal,
in jobs that contain loops this delay can accumulate.
This is the reason why some Jobs may seem to run slower in the Designer
compared to when they run through the console where they run at full speed.
From within the Debugger options,
we can also specify which hotkey should be used to execute the next action
when going through our Job.
This way we can avoid using the mouse that might create conflicts in jobs containing Mouse actions.
Finally,
there is also an option of saving the job we are editing, automatically,
every time we run it through the Jog Designer.
This concludes our short introduction on the debugging features of WinAutomation.
Thank you for watching!