BeforeMenuUnload

[GKusnick]

Can anyone enlighten me on how BeforeMenuUnload is supposed to work? The Studio manual says that it fires "during a menu transition, before the current menu has been unloaded." However this seems not to be true if the transition is triggered by an item on an OptionsMenu. In that case, the current menu simply exits without BeforeMenuUnload ever getting called.

Is this by design? Have I uncovered a bug? Is there some other hook I should be using instead?

[Opus4]

Yes, that was a problem discovered fairly recently. I think it might have been fixed in v4.1.5, but if not, it will be in the next update.

- Andy

[GKusnick]

Thanks for the quick answer. I'm not seeing it mentioned in the release notes for 4.1.5, so perhaps I'll wait for 4.1.6.

[GKusnick]

OK, now here's a question about the other end: BeforeMenuLoad.

I created a dummy menu with three child widgets: an attribute, a BeforeMenuLoad hook, and a panel. I put calls to DebugLog in three places: in the attribute's value, in an Action widget under the hook, and in the Fixed Width property of the panel. On loading the menu I get the following output in the console window:

Sun 1/22 17:49:25.777 Attribute value
Sun 1/22 17:49:25.800 Panel property
Sun 1/22 17:49:25.804 BeforeMenuLoad hook
Sun 1/22 17:49:25.808 Panel property
Sun 1/22 17:49:25.830 Panel property

So it seems that BeforeMenuLoad is not the first thing to happen when a menu is loaded. Attributes and other widget properties are initialized first.

Is this how it's supposed to work?

[Opus4]

Originally Posted by GKusnick

Is this how it's supposed to work?

Pretty much -- some things have to get initialized before anything else can be done.

- Andy

[Opus4]

Update: I finally had a chance to test this in v4.1.5, so I can now say this is fixed. If you transition to a new menu from an OptionsMenu dialog, the menu's BeforeMenuUnload will get called before the menu unloads.

- Andy