Hi,
> Okay, here's a quick run-down of the SetMenu call:
[foo: The menu item attribute to modify]
> 0x6D - Said spec (Yes, you were right!)
> 0x6E - Item text
> 0x6F - Key text
> 0x70 - Enabled flag
Are disabled menu entries grayed out or removed in Sierra SCI?
> 0x71 - Tag value
> I don't really know about 0x71, but the only thing I can think of is
> that it is used internally to maintain the state of, for instance, Sound
> on/off - that's the only place I've seen it used.
Is there any kernel space handling of the tag value, or is it just read
from and written to from script space?
> The SelectMenu() takes an event record as a paramater, plus an optional
> boolean value which apparently has something to do with sound being
> paused or not (It's probably there because SelectMenu() is used in the
> strange manner seen in Hoyle).
Hmm. What does it return? Does it modify the event? Also, is menu
navigation handled from within the interpreter (i.e., if ESC is pressed,
does the interpreter take complete control over the system?)
> > > BTW, this game would be brilliant for testing our menu API's... for each
> > > card game, a game-specific menu is added to the menu bar.
> >
> > So they remove the menus, too?
>
> Yes, they would have to do that.
How is that done? There is an AddMenu() call to add complete menus, a
SetMenu() call to modify menu entries, and SelectMenu() for invoking
menu-associated functionality, but I don't recall seing RemoveMenu().
Do they restart the game to do this?
llap,
Christoph
