AnsweredAssumed Answered

Field Script Triggers disappear after assigning a Button to the field

Question asked by nsturmwind on Dec 28, 2009
Latest reply on Jan 12, 2010 by TSGal

Summary

Field Script Triggers disappear after assigning a Button to the field

Description of the issue

FileMaker Product(s) involved:FileMaker Pro Advanced 10.0v3Operating System(s) involved:Mac 10.5.8Detailed description of the issue:After assigning a button script to a field that has existing assigned script triggers, no script triggers appear in the Set Script Triggers dialog. The red asterisk still appears in the bottom-left corner of the field, and the existing triggers still trigger. (This part of the bug is more-or-less cosmetic.) Futhermore, if new script triggers are assigned (even to events that were not previously assigned) after assigning the button script, the existing triggers no longer trigger. (This part of the bug causes changes to previously assigned settings.) Exact steps to reproduce the issue: [See revised steps in a later message in the thread that more clearly demonstrate the second part of the bug.] 1.  Create a new database.2.  Create a single text field called "Text" and place it on a layout. 3.  Create three scripts called "Trigger Enter", "Trigger Modify", "Button", each containing a Show Custom Dialog step that prints the name of the script (or similar identifying information). 4.  Enter layout mode.  5.  Right-click on the field, select Set Script Triggers... Assign the "Trigger Enter" script to the OnObjectEnter event for Browse mode. Click OK. 6.  Enter browse mode. Verify that the Trigger Enter script displays the dialog when the field is entered. Enter layout mode again. 7.  Right-click on the field, select Button Setup... Select Perform Script and assign the script "Button". Click OK. 8.  Right-click on the field, select Set Script Triggers... Click OK. In step 8 the OnObjectEnter event appears to not be assigned. However, it is still assigned, and this can be verified by the following steps: 9.  Right-click on the field, select Button Setup... Select Do Nothing. Click OK. 10.  Right-click on the field, select Set Script Triggers... Click OK. In step 10 the OnObjectEnter script trigger is visible again.  For the second part of the bug, repeat step 7 to re-assign the button, and then take the following steps: 11.  Right-click on the field, select Set Script Triggers... Assign the "Trigger Modify" script to the OnObjectModify event for Browse mode. Click OK. 12.  Right-click on the field, select Button Setup... Select Do Nothing. Click OK. 13.  Right-click on the field, select Set Script Triggers... Click OK. In step 13 only the OnObjectModify event has an assigned script. 14.  Enter browse mode. Click in the field. Type in the field. In step 14, the "Trigger Enter" script no longer triggers when the field is entered, but the "Trigger Modify" trigger does trigger when data is entered into the field. Expected Result:In step 8, the OnObjectEnter event should show that the "Trigger Enter" script is assigned. In step 13, the OnObjectEnter should show that the "Trigger Enter" script is assigned and the OnObjectModify event should show that the "Trigger Modify" script is assigned. In step 14, the "Trigger Enter" dialog should appear when entering the field, and the "Trigger Modify" dialog should appear when typing in the field. Actual Result:In step 8, the OnObjectEnter event shows no assigned script. In step 13, the only the OnObjectModify event shows that the "Trigger Modify" script is assigned. The OnObjectEnter event shows no assigned script. In step 14, the "Trigger Enter" dialog does not appear when entering the field, although the "Trigger Modify" dialog appears when typing in the field.  Exact text of any error message(s) that appeared:NoneAny workarounds that you have found: Re-assign all field script triggers after assigning a button script to a field.  

Outcomes