16 FileMaker Pro Advanced Development Guide
To change the way functions are sorted in the Define Custom
Functions dialog box, choose a category from the
View list.
Deleting custom functions
When you delete a custom function, it is no longer available for use.
If you have full access privileges to a database and are editing a
calculation that uses a custom function that has been deleted, the name
of the function is replaced with the string <Function Missing>.
To delete a custom function:
1. Choose File menu > Define > Custom Functions.
2. In the list of custom functions, select the function to be deleted and
click
Delete.
3. Continue working with custom functions or click OK.
Duplicating custom functions
You can make a copy of a custom function and then edit the copy to
perform a similar operation.
To duplicate a custom function:
1. Choose File menu > Define > Custom Functions.
2. In the list of custom functions, select the function to be duplicated
and click
Duplicate.
The copy of the function appears in the list of custom functions with
“Copy” appended to its name.
3. Continue working with custom functions or click OK.
About Kiosk mode
Kiosk mode is a way of displaying your database solution or your
runtime database solution on a full screen, without any toolbars or
menus. As the name suggests, Kiosk mode can be used to present your
database to users as an information kiosk. You can design your
database to run through a touch screen.
Database files that open in FileMaker Pro, FileMaker Pro Advanced,
or the runtime application can be transformed into files that must open
in Kiosk mode for all accounts with a specific privilege set. When you
create a solution to run in Kiosk mode, you need to provide navigation
for your solution and the ability for users to quit your solution. For
more information about accounts and privileges, see Help.
Navigating in Kiosk mode
The primary file is the main database that users see first in your Kiosk
solution. Because Kiosk mode does not contain any menus or window
controls, the primary file must contain buttons that users can click to
navigate through the solution, close the files, and to quit
FileMaker
Pro, FileMaker Pro Advanced, or the runtime application.
To decide how users will navigate your Kiosk solution, start by
planning your navigation design on paper. Decide what will happen
when each button is clicked, and give users a way to get back to the
beginning of your solution from each layout. To further control what
users see, create startup scripts that display a specific layout when a
file is opened.
1 If your Kiosk 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 Because Preview mode disables buttons, make sure that any Enter
Preview Mode script step is followed by a Pause/Resume Script script
step and specify an amount of time the script should remain in
Preview mode. Place an Enter Browse Mode script step after the
Pause/Resume Script script step.
Note When a Kiosk solution is open, access to the operating system
is limited. On Windows machines, you can press Alt+Tab to go to
another application from your Kiosk database solution.