Many support requests and forum posts I see include a script snippet and a statement like “this value is wrong” or “the if statement says false but it should be true”. So we make an intelligent guess and say “so perhaps the value you are comparing isn’t what you think it is. Use the debugger”.

Stepping through the debugger reveals answers to problems like this quickly. Another way of checking values is to use a diagnostic message box. Whack a line like this into the script:

MessageModal>%MyVariable%

And see if MyVariable is what you are expecting.

Here’s an article I wrote some time ago on how to use the debugger.

http://www.mjtnet.com/blog/2006/05/17/use-the-debugger/

Use it. Debug. Debug. Debug. Please.

Tweet This

Related posts:

1. Use the Debugger!
2. Associating a File Extension with a Compiled Macro
3. Multiple Monitors aid Productivity and Debugging
4. Thou shalt not waste time doing repetitive and mundane tasks
5. Twittering from Macro Scheduler with the Twitter API

This entry was posted on Wednesday, September 12th, 2007 at 10:18 am and is filed under Scripting. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.