Why did handling of Pause/Resume Script change in FMP9 Script Debugger?

[Kent Searight]

Prior to FMP 9 Advanced the Script Debugger would not let one step past the script step "Pause/Resume Script (Indefinitely)"; rather it just held it up in the paused mode until the user triggered a script in the interface (button) that resumed the current script. I find this behavior much more useful than the current behavior, which is to allow the developer to step past the "Pause/Resume Script (Indefinitely)" because the resumption of the scripts that I have pause is most often accompanied by a script result being passed along by the script of the button. When one can accidentally step past the pause, as I've done on numerous occasions, no result is passed back into the script, rendering the script debugging session useless, at least from the point of pause onward.

Does anyone know why FMI chose to change this behavior in the Script Debugger? Are there any advantages that outweigh the disadvantage mentioned above?

Thanks in advance!

Edited March 19, 2008 by Guest

[mr_vodka]

Hi Kent,

I think it may be due to the new feature of error capturing while running a script in debugger now.