If you’re not using more than one monitor, you are missing out big time. For one thing, some research by the University of Utah found that using two monitors increases productivity 44%. There’s a good summary and more comment on this on the coding horror blog.
A huge benefit of multiple monitors for Macro Scheduler developers is that it makes developing and debugging automation macros a lot easier. When I’m building a script that controls another application I will often put the Macro Scheduler editor on one monitor and the application I’m automating on another. I can then see both side by side, so I don’t need to switch focus back and forth. I can run my macro as I’m developing it and see the script at the same time as the results. If I need to debug I can step through the script and see the progress of the script at the same time as the outcome without the changing of focus effecting it.
Debugging a script that simulates a user and needs to change focus can be a bit of a conundrum, since the act of debugging introduces delays, allowing more time for events to complete, and causes loss of focus. In Macro Scheduler there’s a “Refocus Windows” setting in the Debugger, but even that isn’t enough in some cases. Being able to work on the macro and see the target application at the same time without either interfering with each other is therefore the best solution.
If you don’t have a PC or video adaptor that can support more than one monitor you could use ZoneScreen along with a laptop or second PC to act as your second screen. A single monitor big enough to let you put the editor and target apps side by side without them overlapping would work too.
If you’re stuck with a small monitor and simply can’t have both editor and target application visible at the same time – you may be at a client’s site or working on a notebook – and need to debug code that needs to see the screen, don’t forget you can also set and run to breakpoints. With a breakpoint you can step through the code and at any time run to the next breakpoint, allowing the macro to whizz through the code to that point without switching focus back to the editor between each step. So for crucial sections of code which need to, say, capture a screen or scrape some text, it can be very useful. Once the script reaches the breakpoint you will be returned to the editor where you can continue stepping line by line, or run to the next breakpoint or end.
In my opinion multiple monitors are an absolute must. But there are limits!