Script Triggers
SeedCodeComplete3.ScriptTriggers History
Hide minor edits - Show changes to output
Changed lines 32-39 from:
There are other miscelaneuos triggers in place. The best way to determine if an object has a trigger attached to it or not is to turn on their visibility. In Layout Mode, choose View > Show > Script Triggers. When this is enabled you'll see a little orange scrolly thing on objects with attached triggers.
to:
There are other miscelaneuos triggers in place. The best way to determine if an object has a trigger attached to it or not is to turn on their visibility. In Layout Mode, choose View > Show > Script Triggers. When this is enabled you'll see a little orange scrolly thing on objects with attached triggers.
%center% http://www.seedcode.com/rootimages/stikipad/complete13/Show.png
When this is enabled you'll see a little orange scrolly thing on objects with attached triggers.
%center% http://www.seedcode.com/rootimages/stikipad/complete13/ObjectTrigger.png
%center% http://www.seedcode.com/rootimages/stikipad/complete13/Show.png
When this is enabled you'll see a little orange scrolly thing on objects with attached triggers.
%center% http://www.seedcode.com/rootimages/stikipad/complete13/ObjectTrigger.png
Changed lines 3-12 from:
-> '''1.''' Determine if
->
->
Finally, all "real" layouts (not printing layouts or mini-windows) are running an OnLayoutExit script trigger that feeds the back and fwd system
to:
All user interface layouts make extensive use of layout based Script Triggers, and in general will probably not need to be modified too much. Fortunately these script triggers follow the same pattern across these different layouts/modules. Contacts has 7 script triggers with these general purposes:
->'''Contact On Record Load:''' Initializes Global variables and fields to manage panel navigation. This trigger also fires when new records are created to put the user in [[Edit Mode]].
->'''Contact On Commit''' and '''Contact On Revert:''' Manages entering and exiting [[Edit Mode]].
->'''Contact On Layout Exit:''' Clears Gloabal variables and fields used for that layout.
->'''Contact On Mode Enter''' and '''Contact On Mode Exit''' Manages entering and exiting [[Find Mode]] by navigating to the Find Panel and back.
->'''Contact On View Switch''' Manages entering and exiting List View by clicking View Buttons on the Menu Bar. This trigger is used by WebDirect to fire the script as Custm Menus are not supported in Web Direct.
->'''Contact On Record Load:''' Initializes Global variables and fields to manage panel navigation. This trigger also fires when new records are created to put the user in [[Edit Mode]].
->'''Contact On Commit''' and '''Contact On Revert:''' Manages entering and exiting [[Edit Mode]].
->'''Contact On Layout Exit:''' Clears Gloabal variables and fields used for that layout.
->'''Contact On Mode Enter''' and '''Contact On Mode Exit''' Manages entering and exiting [[Find Mode]] by navigating to the Find Panel and back.
->'''Contact On View Switch''' Manages entering and exiting List View by clicking View Buttons on the Menu Bar. This trigger is used by WebDirect to fire the script as Custm Menus are not supported in Web Direct.
Changed lines 19-20 from:
You can certainly turn off individual triggers by setting them not to operate in browse mode.
to:
You can certainly turn off individual triggers by setting them not to operate in browse mode.
Changed lines 23-29 from:
-> $$sc_ScriptTriggers_Off
... to 1. Just be sure to set it back to "" or 0 when you're done. You can see an example of this in the script "Collapse Side Bar ( Action )"
Note that we also have a nice script you can call that will stop layout-based script triggers. You'll likely want to preface any new scripts you assign to layout based triggers with a call to this "Halt Layout Based Script Triggers" script. This stops the
to:
'''But Remember''' all of the above functionality is an important part of how SeedCode Complete works, so do take care when doing this.
!! What kinds of object based script triggers are in use?
The most common use of object based script triggers in SeedCode Complete is [[Type Aheads]] for [[Portal Filters]] and [[Selectors]]. but they are used in some other places as well.
Another common place object triggers are used are on Tab and Slide controls so we can use the On Object Modify trigger to launch a script after the tab is brought into focus. More details on this in [[Object Navigation]].
There are other miscelaneuos triggers in place. The best way to determine if an object has a trigger attached to it or not is to turn on their visibility. In Layout Mode, choose View > Show > Script Triggers. When this is enabled you'll see a little orange scrolly thing on objects with attached triggers.
!! What kinds of object based script triggers are in use?
The most common use of object based script triggers in SeedCode Complete is [[Type Aheads]] for [[Portal Filters]] and [[Selectors]]. but they are used in some other places as well.
Another common place object triggers are used are on Tab and Slide controls so we can use the On Object Modify trigger to launch a script after the tab is brought into focus. More details on this in [[Object Navigation]].
There are other miscelaneuos triggers in place. The best way to determine if an object has a trigger attached to it or not is to turn on their visibility. In Layout Mode, choose View > Show > Script Triggers. When this is enabled you'll see a little orange scrolly thing on objects with attached triggers.
Changed lines 15-16 from:
You can certainly turn off individual triggers by setting them not to operate in browse mode. This keeps the trigger tied to the object in case you want to turn it back on later. If you haven't done this before, check out the section on Script Triggers in FileMaker's built in Help.
to:
You can certainly turn off individual triggers by setting them not to operate in browse mode.
This keeps the trigger tied to the object in case you want to turn it back on later. If you haven't done this before, check out the section on Script Triggers in FileMaker's built in Help.
This keeps the trigger tied to the object in case you want to turn it back on later. If you haven't done this before, check out the section on Script Triggers in FileMaker's built in Help.
Changed lines 23-25 from:
... to 1. Just be sure to set it back to "" or 0 when you're done. You can see an example of this in the script "Collapse Side Bar ( Action )"
to:
... to 1. Just be sure to set it back to "" or 0 when you're done. You can see an example of this in the script "Collapse Side Bar ( Action )"
Note that we also have a nice script you can call that will stop layout-based script triggers. You'll likely want to preface any new scripts you assign to layout based triggers with a call to this "Halt Layout Based Script Triggers" script. This stops the script is the layout is drawn off screen or has a name other than the solution's main window name. For an example of this, see the beginning of the script "On Project Record Load".
Note that we also have a nice script you can call that will stop layout-based script triggers. You'll likely want to preface any new scripts you assign to layout based triggers with a call to this "Halt Layout Based Script Triggers" script. This stops the script is the layout is drawn off screen or has a name other than the solution's main window name. For an example of this, see the beginning of the script "On Project Record Load".
Changed lines 5-6 from:
-> '''1.''' Determine if the layout should be shown with or without the [[side bar]]. So you'll see simple layouts like "Contacts" calling the "Show Side Bar by Preference" script. You can set this side bar preference, by the way in the script "Load Settings - On Startup --- Edit Configuration Here ---"
to:
-> '''1.''' Determine if the layout should be shown with or without the [[LeftHandSideBar | side bar]]. So you'll see simple layouts like "Contacts" calling the "Show Side Bar by Preference" script. You can set this side bar preference, by the way in the script "Load Settings - On Startup --- Edit Configuration Here ---"
Changed lines 5-6 from:
-> '''1.''' Determine if the layout should be shown with or without the side bar. So you'll see simple layouts like "Contacts" calling the "Show Side Bar by Preference" script. You can set this side bar preference, by the way in the script "Load Settings - On Startup --- Edit Configuration Here ---"
to:
-> '''1.''' Determine if the layout should be shown with or without the [[side bar]]. So you'll see simple layouts like "Contacts" calling the "Show Side Bar by Preference" script. You can set this side bar preference, by the way in the script "Load Settings - On Startup --- Edit Configuration Here ---"
Added lines 1-12:
!! What kinds of layout based script triggers are in use?
Many layouts in Complete have an OnLayoutEnter trigger attached to them, and these triggers are trying to accomplish one or more of these three things:
-> '''1.''' Determine if the layout should be shown with or without the side bar. So you'll see simple layouts like "Contacts" calling the "Show Side Bar by Preference" script. You can set this side bar preference, by the way in the script "Load Settings - On Startup --- Edit Configuration Here ---"
-> '''2.''' The calendar layouts employ this script as well, but call it from within their own OnLayoutEnter triggers which manage the calendar's refresh.
-> '''3.''' Some special layouts have triggers to make sure global variables are set or cleared as you move from record to record. So you'll see the Projects layout has an OnRecordLoad script trigger as well to manage these processes.
Finally, all "real" layouts (not printing layouts or mini-windows) are running an OnLayoutExit script trigger that feeds the back and fwd system.
Many layouts in Complete have an OnLayoutEnter trigger attached to them, and these triggers are trying to accomplish one or more of these three things:
-> '''1.''' Determine if the layout should be shown with or without the side bar. So you'll see simple layouts like "Contacts" calling the "Show Side Bar by Preference" script. You can set this side bar preference, by the way in the script "Load Settings - On Startup --- Edit Configuration Here ---"
-> '''2.''' The calendar layouts employ this script as well, but call it from within their own OnLayoutEnter triggers which manage the calendar's refresh.
-> '''3.''' Some special layouts have triggers to make sure global variables are set or cleared as you move from record to record. So you'll see the Projects layout has an OnRecordLoad script trigger as well to manage these processes.
Finally, all "real" layouts (not printing layouts or mini-windows) are running an OnLayoutExit script trigger that feeds the back and fwd system.
Changed lines 7-8 from:
$$sc_ScriptTriggers_Off
to:
-> $$sc_ScriptTriggers_Off
Added lines 1-9:
!! Can I turn script triggers off?
You can certainly turn off individual triggers by setting them not to operate in browse mode. This keeps the trigger tied to the object in case you want to turn it back on later. If you haven't done this before, check out the section on Script Triggers in FileMaker's built in Help.
You can also temporarily disable triggers by setting the variable...
$$sc_ScriptTriggers_Off
... to 1. Just be sure to set it back to "" or 0 when you're done. You can see an example of this in the script "Collapse Side Bar ( Action )"
You can certainly turn off individual triggers by setting them not to operate in browse mode. This keeps the trigger tied to the object in case you want to turn it back on later. If you haven't done this before, check out the section on Script Triggers in FileMaker's built in Help.
You can also temporarily disable triggers by setting the variable...
$$sc_ScriptTriggers_Off
... to 1. Just be sure to set it back to "" or 0 when you're done. You can see an example of this in the script "Collapse Side Bar ( Action )"
