Database Reference
In-Depth Information
OnGestureTap
OnGestureTap
fires when a tap gesture is received on a layout in FileMaker Go. It runs be-
fore the event is processed and can be used in Browse and Find modes. It's cancelable with a
False value in an
Exit Script
step.
Object Triggers
To configure an object's triggers, select the object and then choose Format→Set Script Trig-
gers. The resulting window shows you the triggers available for the object. (
Figure 11-23
)
.
You can apply triggers only to fields, tab controls, portals, buttons, and web viewers. For
some triggers, the behavior of a script trigger may be slightly different, so expect to test
scripts fired by triggers until you get used to their intricate ways. You can't attach a trigger to
a text label, line, shape, or picture. The Set Script Triggers command will be grayed out
when those objects are selected. The new
OnPanel Switch
script trigger is grayed out ex-
cept when you have a tab control or other panel object selected.
Object triggers sound picky when you scan through their names (and to a degree they are),
but that's just to give you as much control about when they fire as possible. As you read
through this list, you'll see that object triggers appear in the same order as users interact with
an object, in this case, say, a field. So for any particular interaction with a field, the following
actions might take place:
▪ The field is
entered
—when you click in it.
▪ The field is
modified
—you type new data into it.
▪ The field's
validation
kicks in—you click out of the field.
▪ The field's new data is
saved
—FileMaker's autosave makes the new data permanent.
▪ The field is
exited
—a new object is entered or the record is committed.
And there's even one more action that can take place on an object. As with layouts, you can
have each keystroke trigger a script. As you'll see in this section, the better you understand
how FileMaker handles objects, the easier it is to apply the proper object trigger.
