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.
Do I have to call MenuEraseStatus(0) every time a shortcut is called or can
I just do it once at program startup?
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 :).
Thanks,
Mike McCollister
> ----------
> From: David Fedor[SMTP:[EMAIL PROTECTED]]
> Reply To: [EMAIL PROTECTED]
> Sent: Wednesday, November 10, 1999 9:02 PM
> To: [EMAIL PROTECTED]
> Subject: Re: MenuEraseStatus(0);
>
> >> Recently I found that if I use MenuEraseStatus(0) right after I get a
> menu
> >> event that this problem goes away. Does anyone know what this is doing?
>
> That's the right thing to do, if you're going to be drawing to the bottom
> area of the screen in response to a menu command that has a shortcut. The
> system will call it for you, if you're popping up another form, or some
> other things like that which will almost always need it.
>
> What's more, you'll have more situations in which calling
> MenuEraseStatus()
> is appropriate, when running on 3.5 and higher where you'll have the
> command toolbar which covers more area.
>
>
> > well.. the following code is probably better (passing 0 may lead
> > to unwanted effects).. :>
> >
> > MenuEraseStatus(MenuGetActiveMenu());
>
> I just checked the sources from 3.5 back to 3.0 inclusive, and in every
> case passing 0 is equal to passing MenuGetActiveMenu(), except passing 0
> is
> faster :-)
>
> -David Fedor
> Palm Developer Support
>
>
>
