Developer’s Guide
Table Of Contents
- Chapter 1 Getting started
- Chapter 2 Using FileMaker Developer features
- Chapter 3 Using the Developer Utilities
- Overview of preparing your solution files
- Modifying database solution files
- Considerations for a runtime database solution
- Binding databases into runtime database solutions
- Saving and reusing Developer Utilities settings
- Converting and upgrading solution files
- Removing full access privileges from databases
- Chapter 4 Distributing runtime database solutions
- Chapter 5 Customizing database solutions
- Chapter 6 Creating custom layout themes
- Chapter 7 Developing third-party FileMaker plug-ins
- About external functions
- About the example plug-in
- Installing, enabling, and configuring the example plug-in
- Description of the FMExample plug-in’s external functions
- Using the example plug-in
- Customizing the plug-in example
- Requirements for writing external function plug-ins
- FileMaker messages sent to the plug-in
- Avoiding potential Mac OS X resource conflicts
- Providing documentation for your plug-in
- Registering your plug-in
- Appendix A Feature comparison of the runtime application with FileMaker Pro
- Index
Using FileMaker Developer features 13
If a script with access privileges set to Modifiable performs a script
with Executable Only access, the Executable Only script will
perform in its entirety without showing its steps in the Script
Debugger. If an Executable Only script performs a script with
privileges set to Modifiable, only the steps in the Modifiable script
will appear in the Script Debugger. For more information about
script privileges and running scripts with full access, see Help.
To run scripts in debug mode, select Scripts menu > Debug Scripts.
Note In order to facilitate proper script debugging, the Script
Debugger overrides some script steps. The Allow User Abort script
step with the option set to off will not prevent you from stopping the
execution of a script. The Adjust Window script step with the options
of hide or minimize will not hide or minimize the window when
encountered through the Step or Step Into buttons.
Choose To
Step Execute the script one step at a time.
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. The Script Debugger will execute all
sub-script steps until it encounters a breakpoint.
Step Into Execute the script one step at a time.
If the script step is Perform Script, the Script Debugger
will step to the first line of the sub-script and await user
input before proceeding to the next sub-script step.
Step Out Execute 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.
If the script is not a sub-script, the Step Out command
will cause the Script Debugger to execute all script and
sub-script steps until it encounters a breakpoint.
Run Execute all script steps until a breakpoint is encountered.
Stop Execution Halt execution of a script and close Script Debugger.
Set Next Step Set the step execution pointer to the highlighted script
step.
This command passes control to the highlighted step but
does not perform the step. The highlighted step is
performed when script execution is resumed. Any script
steps between the last executed step and the assigned next
step are not executed. Click a step to highlight it, then
click the Set Next Step button.
Set/Clear
Breakpoint
Set or clear a breakpoint from the selected line.
Breakpoints can be set or cleared from the Script
Debugger or from ScriptMaker. Breakpoints are saved
with the file that contains the script. Breakpoints are
ignored by FileMaker Pro and when the Script Debugger
is not in use. Breakpoints allow the Script Debugger to
perform large sections of the script that do not need to be
looked at closely.
Remove
Breakpoints
Clear all the breakpoints from the current script.
The Remove Breakpoints command is only in the Debug
menu.
Go To ScriptMaker Halts script execution and opens ScriptMaker so you can
edit the script.
The command to open ScriptMaker does not appear in the
Debug menu.
Choose To