MP1454

Looks like I did get debugging output showing each line executed. But I still would like to know how to set breakpoints and have the debugger stop and then press a function key to step through my code.

I compile and Go with F5 and get console and FileWrite output, but how do I set breakpoints and/or step through my code? I need to debug if some If branch tests are successful and in particulare why my StringReplace lines are not working.

Thanks ioa747. I have added that directive, but then what? I tried F9 when on a line in the code, but nothing happens. Isn't it supposed to put a red dot on the left? It's too bad there isn't a comprehensive tutorial on debugging AutoIt scripts. Maybe I could write one if I ever get this figured out.

Hello gurus, I've been trying to figure out how to debug autoit scripts in the SciTE editor and not having much luck finding any workable information. I have the full version SciTE4AutoIt3 21.203.1500.3 and AutoIt v3.3.16.1 installed in Windows 10. I'm not finding anything mentioned about debugging in AutoIt Help. I've run web searches for "debug autoit3 scripts with SciTE" but have only found bits and pieces of things that don't work and don't have a complete picture of what is needed for code debugging. Is there a tutorial or something giving instructions on what is needed to enable the debugger, set breakpoints, walk through my code, display runtime values, etc.? I would really appreciate pointers to how to debug au3 scripts, as I keep running into trouble spots in my code and would rather not just depend on ConsoleWrites to get the information I need. Any pointers or hints would be greatly appreciated. MarkP

I found the issue. In earlier pre-Excel versions of my script I had no problems opening files without a path, assuming the files were in the same folder as the script or compiled executable, which they were. Everything worked fine. But with _Excel.au3, I got the error until I replaced $sourceFile with the full path. So that was the issue. Interesting enough, if I use a relative path ".\Test.xlsx" it opens a blank Excel instance and just sits there. Doesn't abort; doesn't open the spreadsheet. So there you go, _Excel.au3 is limited in that it has to have a full file path, unlike the built-in FileOpen() which works fine without a full path. Thanks for at least replying to my call for help.

Gurus, I'm getting @error = 3 on _Excell_BookOpen on an AutoIt Version 3.0 console app and I don't know what I'm doing wrong. I haven't found any working examples of just reading through an existing spreadsheet. Any help would be greatly appreciated. It's an Excel 365 spreadsheet on Windows 10. Here is my code sample: #include <Excel.au3> $sourceFile = "Duplicates.xlsx" If Not FileExists($sourceFile) Then ConsoleWrite("Oops, don't see '" & $sourceFile & "'" & @LF) Exit EndIf $oExcel = _Excel_Open();False,False,False,False,False) ; hidden instance If @error Then ConsoleWrite("Failed to open spreadsheet") Exit EndIf $oWorkbook = _Excel_BookOpen($oExcel,$sourceFile,True,False) ; readonly If @error Then ConsoleWrite("Excel UDF: _Excel_BookOpen, Error opening '" & $sourceFile & "'." & @CRLF & "@error = " & @error & ", @extended = " & @extended) _Excel_Close($oExcel) Exit EndIf Doing a Test Run or running the commandline compiled exe I get What am I doing wrong? MP1454

Thank you argumentum for you reply. When I run your script the DBUG window opens up, but I have no idea what to do next. I need to do a lot of reading on this debugger to learn how to use it. Thanks for getting me started with it though. In the meantime, I need to sort out different issues with the GUI functions.

Sorry, been under a crunch to get the application working and haven't had a chance to follow up on this. I added some FileWrite lines and figured out what was going on with my script, so I didn't need to get the debugger working for AutoIT3 Beta. Next time I will take the time to strip down the code to submit, but I'm guessing the stripped down version won't have the problem. Thanks for the response.

Hello, I'm relatively new to AutoIt3 and have an app where I'm using Map, therefore I run it in Beta. I need to debug my script. When I use the graphical debugger Version 0.47.0.0 (which is working perfectly with other scripts of mine), the Beta option is grayed-out despite "Check for Updates" showing I have Beta version 3.3.15.3 installed along with production version 3.3.14.5. Failing that, for the first time I tried _Debug. When I do a Beta Run, the SendMessage.au3 file opens up in the SciTE editor with a "missing EndIf" message on line 20. What the heck is going on? Is SendMessage.au3 used by Debug.au3 and why am I getting an error message in something that is not my script? If someone has a suggestion for either of these issues, I would really appreciate it.