> One other question before I commit my code to this. Is there a way for me to
> wait for the menu command shortcut to disappear? I wouldn't mind waiting for
> that to dissappear before I update my display.
the menu command shortcut is erased after the event handling code.
if you need to wait for it.. then do something like this:
// start menu option processing
// do operations based on the menu option
// - but dont draw to screen
MenuEraseStatus(NULL); // or whatever
// draw to the screen
> Do I have to call MenuEraseStatus(0) every time a shortcut is called or can
> I just do it once at program startup?
you will have to do it every time the short cut is called. in the
above psuedo code.. if you leave the MenuEraseStatus(NULL) until
last.. you might still see the command shortcut :> if you do it
too early.. you wont see it at all :(
> Also, what is the official name of that shortcut name thingie at the bottom
> of the screen? I just want to make my program documentation sound
> intelligent :).
menu shortcut?
or.. more appropriately with the function call: MenuStatus :>
cheers.
az.
--
Aaron Ardiri
Lecturer http://www.hig.se/~ardiri/
University-College i G�vle mailto:[EMAIL PROTECTED]
SE 801 76 G�vle SWEDEN
Tel: +46 26 64 87 38 Fax: +46 26 64 87 88
Mob: +46 70 656 1143 A/H: +46 26 10 16 11
