DEBUG USE - break point, etc.

[jdpmdphd]

Unable to find adequate documentation or simple walk through example.

Tried appending a line with ;*[mybreak1]
then ^D
then alt-E
but it did not act like a break point, ran right past to the end.

[maestrith]

After you add in a breakpoint try Alt+M Refresh Project Explorer{Enter} then try to run the debug again.

[jdpmdphd]

Thank you very much for your prompt response. Your refresh advice worked for a single test.ahk file, but did not work in another with break in an included file. The include shows up in the updated project, but does not stop there to break despite your recommended refresh followed by ^D started in the calling file, followed by alt-E. Documentation with simple and complex debug step by step illustration would be very helpful, and I suggest adding that to your web page. e.g. testDebug.ahk : obj:=[] a=1 obj.push(a) b=a+10 ;* [break for B] obj.push(b) #include testInclludedFile.ahk testIncludedFile.ahk : c=b+100 ;* [break for C] msgbox,4096,%A_LineNumber%, a=%a% b=%b% c=%c ;* [break after msg] d=c+1000 ;* [break for D] msgbox,4096,%A_LineNumber%, DONE return TO DEBUG:in 1. insert the * [breaks] 2. [if fresh breaks, save and !m Refresh Project {Enter}] 3. ^D 4. !E 5 ... instruct what to do to pause, inspect variables including objects, go line by line vs jump to next break point, change values, execute /*option code*/ Thanks and be well, Dr. Justin Pearlman

…

On Mon, Apr 6, 2020 at 9:28 PM Chad Wilson ***@***.***> wrote: After you add in a breakpoint try Alt+M Refresh Project Explorer{Enter} then try to run the debug again. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA5MFFKCH2EG62ZU3ARLM3RLJ6SVANCNFSM4MCQ7FJA> .

-- Thank you for your consideration. Best regards, Justin D. Pearlman MD PhD MA

[tdalon]

I support this request. Struggling to find out how debugging with breakpoints work in AHK Studio

[jdpmdphd]

I have AHK studio too, but have been happier with SCITE mostly - most steps are more obvious and easier to get into fingertip memory with Scite, search is nicer, plus you can customize it fairly easily. My issue with break points is: sometimes it does not give you access to program code and acts frozen/non-responsive instead. Right click on program then allows you to quit. I can do work around by inserting just prior to break ;if debug msgbox,4096,%A_LineNumber%,% " " ; ... then click on stop || button, then -> single step, then OK on the message but I was writing to seek a simpler reliable solution eg have SCITE offer to step forward with okay message if stopped greater than x seconds.

…

On Wed, Oct 21, 2020 at 5:54 AM Thierry Dalon ***@***.***> wrote: I support this request. Struggling to find out how debugging with breakpoints work in AHK Studio — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA5MFAWL7EXS2UJHYBIX43SL2VUXANCNFSM4MCQ7FJA> .

-- Thank you for your consideration. Best regards, Justin D. Pearlman MD PhD MA