This command passes control to the highlighted step but does not perform the step. Set the step execution pointer to the highlighted script step. If the script is not a sub-script, the Step Out command will cause the Script Debugger to execute all remaining script and sub-script steps until it encounters a breakpoint. If the script step is Perform Script, the Script Debugger will step to the first line of the sub-script and wait for user input before proceeding to the next sub-script step.Įxecute all script steps in the current script and, if the script is a sub-script, return to the line after the Perform Script step in the calling script. The Script Debugger will execute all sub-script steps until it encounters a breakpoint.Įxecute the script one step at a time, as well as enter and show steps in sub-scripts. If the script step is Perform Script, the Script Debugger will execute the sub-script, and proceed to the next line of the calling script. Use these controls to debug the script:Įxecute the script one step at a time without entering sub-scripts.To save all open scripts and then debug the script, hold down Shift (Windows) or Option (macOS) and click. Choose Scripts menu > Script Workspace, select your script, then click.Choose Tools menu > Script Debugger, then run your script.Enable the Script Debugger by doing one of the following:.
The Script Debugger is an interactive tool for troubleshooting your FileMaker scripts.įor example, you can you debug scripts that are run from the Scripts menu or keyboard shortcuts debug a script activated by a script trigger, button, or custom menus and temporarily disable or enable script triggers while you work in the Script Debugger To debug scripts: Note This feature is available when the Use advanced tools general preference is selected.
0 kommentar(er)
