Guest MagratGarlick Posted April 29, 2004 Share Posted April 29, 2004 Searching through the forums I find that the only way to debug a script is to "REM" out all the lines then remove the "REM's" line by line until the problem is found. It this correct? I have a script for installing an application that worked fine in my test WinXP setup, but falls over - enters the wrong information in the Product Key - when I run it my main WinXP setup. It would be so useful to be able to step through the script line by line to see what exactly is happening. TTFN Magrat Link to comment Share on other sites More sharing options...
CyberSlug Posted April 29, 2004 Share Posted April 29, 2004 Things that might help: Opt("TrayIconDebug", 1) ;put at beginning of script ; hover over the tray icon to get current script line number Use MsgBox or TrayTip to display results after every line Full Debug features will be added soon. Hope that helps P.S. You can also use #cs and #ce to comment out a block of lines. Use Mozilla | Take a look at My Disorganized AutoIt stuff | Very very old: AutoBuilder 11 Jan 2005 prototype I need to update my sig! Link to comment Share on other sites More sharing options...
scriptkitty Posted April 29, 2004 Share Posted April 29, 2004 As long as there is no major flaws, you can step it through by setting up stops as well, or turn on the tray icon debug option. Hotkeyset("{pause}","pause") $pause=1 ; code $x=1; just an example pause() ; more code $x="this part is cool" pause() func pause() $pause=NOT $pause while NOT $pause tooltip($x,0,0); if you want some tip in it sleep(10) wend tooltip("") endfunc AutoIt3, the MACGYVER Pocket Knife for computers. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now