Script Debugger Buttons

[Jarvis]

I have just started working with the script de-bugger and I have some questions:

The buttons are labeled:

STEP

STEP INTO

STEP OUT

RUN TO BREAKPOINT

STOP EXECUTION

SET NEXT STEP

SET/CLEAR BREAKPOINT

GO TO SCRIPT

What is the difference between STEP & STEP INTO?

What is the difference between STEP OUT & STOP EXECUTION?

Is there a way to activate and deactivate the script debugger without selecting it in the SCRIPTMAKER dialog box?

Thanks!

Jarvis

[QuinTech]

1. If you have subscripts, STEP will run the subscript without getting into the details. STEP INTO will take you step-by-step through the subscript.

2. STEP OUT will take you through the remaining steps of the subscript (not step-by-step) and back to the originating script. STOP EXECUTION stops all scripts right where they're at.

If you have no subscripts, then STEP/STEP INTO operate the same, and STEP OUT/STOP EXECUTION run the same.

3. I don't think so, but there are always clever people here who know more tricks than i.

HTH

Jerry

[smorr]

"Step" is sometimes known as "Step Over" -- it will not enter any subscripts (but it will execute the subscript) (ie steps over the subscript)

"Step into" will move the debugger into any subscripts

"Step out" will execute the rest of a subscript and then return the debugger to the next line of the script that called the subscript

"Stop Execution" will stop the script altogether (without executing any more steps)

Activating the debugger

As far as I know there is no way except the checking the debugger option in the scripts menu of FMDev

Though it would be nice to have a check box in the script editor dialog (FMI are you listening)

And it would be nice to actually open the script for editing from the debugger rather than just the script editor. (FMI -- really? are your listening???)

[The Shadow]

A friend found this one: On the Mac (at least), you can use shift when selecting "Perform" from ScriptMaker's dialog and the "Debug Scripts" toggle will be turned on for you before the script starts.

[QuinTech]

Thanks for that, Shadow... unfortunately doesn't work on Windows, nor does any combination of Ctrl, Shft, or Alt. (FM Dev 6... i don't know about v7.) Anyone know a Windows shortcut?

Jerry

[brownees]

The Script Debugger is enabled in Windows from the Define Scripts dialogue box by selecting the script, pressing Shift and clicking the Perform button.

[QuinTech]

Maybe in version 7 it is ... can't get it to work in 6.

J