Script Triggers and PopUp Field Types

[Jim Lah]

I have noticed different behaviours between using PopUp field types and other field types (Drop Down, Calendar etc), especially as to the values which can be grabbed by the Get (ActiveFieldContents) script step.

In all other field types - the script step grabs the previous field value, whereas with a popup style, the new entered value is grabbed.

Also noted is that PopUp requires an explicit commit (either scripted or by mouse clicking) and therefore has a different result when using Tab Orders on a layout.

The attached file may be of interest to those trying to use script triggers as it demonstrates the impact of different field styles and different script triggers.

If anyone can explain why PopUp is different to the rest, and whether it's a feature or a bug it would be interesting to know. Currently this issue prevents me from using the more desirable PopUp in some of my programmes.

Jim

POC_ScriptTriggers___Popups.fp7.zip

[Fitch]

Good information, thanks. This is covered in the tech brief "Using Script Triggers in FileMaker Pro" on page 34:

"Interaction with popup menus, list, calendar, and auto-complete

A popup menu blocks other events from occurring. Therefore, an OnObjectEnter

script trigger will not run a script until after the menu is dismissed. The layout

object will not register that a change has occurred until an item is picked and the

menu is closed. Therefore, OnObjectModify, Save, and Exit scripts run afterwards

and will not interact with the popup menu."

I can't seem to find the download link for the document, it may be TechNet only.

[mr_vodka]

Tom is correct. The document is TechNet only.

[Jim Lah]

Ah, yes found it on Technet, thanks.

Jim