Anomalous OnLayoutEnter Behavior

[jmci]

My File Close script navigates to a splash screen layout. The OnLayoutEnter triggered-script for this layout installs a menu set with almost no options.

When the file opens, the splash screen layout is the current layout (as intended) and my Startup script pauses for two seconds, does several other things, then navigates to my Home layout. The OnLayoutEnter triggered-script for the Home layout installs a menu set with many more menus and options and all is well.

The problem is that immediately after program execution exits from the Startup script, the OnLayoutEnter triggered-script for the splash screen layout executes and installs the stripped-down menu set. What causes that script to execute?

[Vaughan]

Why are you using the "install menu set" step so often? Each layout has a menu set defined to it, just set the menu set there.

[jmci]

Several of my layouts have two menu sets. One is used when the file is in development mode and contains menus and options that are not included in the menu set that gets installed when not in development mode.

My Splash Screen layout is one of those with two possible menu sets. The Splash Screen layout also serves as an About layout and when the user navigates to that layout I want to present the user with a minimum of menu options. On the other hand, when in development mode, I want many of those menu options available to me.

What I can't understand is how the OnLayoutEnter trigger of the splash screen layout could execute a script after my startup script had already navigated away from that layout to the Home layout several steps before the Exit Script step.

[Vaughan]

I leave the custom menus in place and use the Tools menu to switch menu sets manually.

[jmci]

That's an interesting choice. Now, back to my problem...

I reasoned-out the cause of the problem by myself. The OnLayoutEnter trigger of the Splash Screen layout must have fired when the file first opened but, since I had already assigned my Startup script to run at file open, the triggered script couldn't execute until the Startup script had finished. Of course by that time the Startup script had already navigated to the Home layout but the triggered script still went ahead and installed the menu set that belonged to the Splash Screen layout.

To test this theory I un-checked the OnLayoutEnter trigger from the Splash Screen script. I then modified my Layout_Navigate script to install the custom menu set for the Splash Screen script whenever a user explicitly navigated to the Splash Screen (About) layout. I then closed and re-opened the file and the Home layout appeared with its proper menu set in place.

Problem solved and I've learned a little more than I knew before about the OnLayoutEnter script trigger.