Developer’s Guide
Table Of Contents
- Chapter 1: Installing FileMaker Pro Developer Edi...
- Chapter 2: Binding solution files
- The binding process—an overview
- Before binding
- Binder and runtime terminology
- Specifying the primary file
- Naming the runtime solution
- Assigning the binding key
- Choosing auxiliary files
- Choosing binding options
- Assigning the three-character extension
- Specifying a location for solution files
- What happens during binding
- Binding cross-platform solutions
- Changing solutions
- Chapter 3: Preparing and managing runtime soluti...
- Chapter 4: Distributing your bundled solution
- Appendix A: Feature comparison—runtime Appendix ...
- Appendix B: About the TechInfo database
- Index
Binding solution files 2-9
Design tips for Kiosk mode
Start by planning your database design on paper. Decide what will
happen when each button is selected, and give users a way to get back to
the beginning from each layout.
1 If your solution will be run with a touch screen, use large buttons and
allow space between buttons.
1 Try to limit the number of options available on one screen.
1 Preview mode disables buttons; make sure you create a script to
return you to Browse mode by choosing Continue or pressing the
Enter key. If you have a script that enters Preview mode and end users
won’t have access to a keyboard, follow it with the Pause/Resume
Script step and specify an amount of time the script should remain in
Preview mode. Then have the script return to Browse mode.
In Kiosk mode, it is often desirable to center solution files on the screen.
To center your files, create a startup script that zooms the window.
Using the Toggle Window script step with the zoom option will perform
two actions in Kiosk mode:
1 snap solution file windows to fit layout objects at the right and bottom
edges of the layout
1 center the windows on the screen if the window is smaller than the
available screen area
Important Before using the Toggle Window script step, perform any
script steps that affect the window display area (such as Go to Layout or
Toggle Status Area). Once the window area is determined, add the
Toggle Window script step.
The Toggle Window script step may cover up a window that has an
Exit/Quit button. Be sure that you can navigate to somewhere that
allows you to close the solution elegantly.
Permanently remove access to Define Fields, Define Relationships,
ScriptMaker, and Access Privileges
In the third panel of the FileMaker Pro Binder application, when you
select the Permanently remove access to Define Fields, Define Relationships,
ScriptMaker, and Access Privileges option, access to these areas is
permanently unavailable in solution files. This prevents end users from
modifying the database structure in all solution files.