Mac menubar

[Shari]

>It's a non-standard interface though and a HC capability that is way 
>too abused (backdrops being another. I hate backdrops.) There are a 
>couple of other ways to handle the menu issue, one harder than the 
>other. I usually script the menus so that when a user chooses a menu 
>item that isn't relevant to the auxilliary stack, I close up the 
>auxilliary and return to the main stack before implementing the 
>command. If necessary, add a closestack handler to the auxilliary to 
>clean up or to warn the user so the action can be aborted.
>
>The other way, which is simpler, is to just disable non-relevant 
>menus or menuitems when an auxilliary is opened. If appropriate, 
>sometimes I disable the entire menu -- for example, when the About 
>box is opened.

None of the stacks have a menubar except one,  and from what I've 
read, if there is no menu in a stack, a default menu will be used.  I 
played with that and the results were very bad.

The main stack is just a splash stack, and has no menu.  The only 
stack with a menu is embedded.  And it calls other stacks from time 
to time.  The menus are pretty specific to the one stack, and require 
it to be topmost to function.

The auxilliary stacks don't need the menus, nor does the "main" splash stack.

Disabling the menugroup on suspendStack forces the Metacard menu to 
appear.  In fact, just opening an auxilliary stack forces the 
Metacard menu bar to appear, as they don't have their own menus.

I'm not sure what will happen once it's a standalone.

-- 
--Shareware Games for the Mac--
http://www.gypsyware.com