Currently I work a lot with the script triggers in FileMaker 10. They are a great tool to create a user-friendly interface. But working so intensively with triggers also reveals some missing features. For example, a script trigger is active all the time. As soon as a trigger event is assigned to a script, it will always fire, whenever the event occurs. But this effect is not always welcome. The script command New Window opens a new window with the current layout. If it has any layout triggers assigned, it will fire and process the related scripts.
Before FileMaker 10, when we were using plug-ins like zippScript, we had the chance to disable the triggers. Something similar I like to see in a future FileMaker version: a way to deactivate triggers. And chip in an effective trigger management:
- Controlled trigger deactivation (hard- and soft-coded)
- Trigger logs with information about the trigger event
- Additional trigger information, e. g. a list of all defined triggers for the current layout (perhaps in the Layout Setup window)
- Enhanced Script Debugger with more control regarding trigger events, e. g. a ‘Pause on trigger event’ option