FWIW the Windows implementation sends SALEVENT_MENUACTIVATE and then
SALEVENT_MENUDEACTIVATE whenever the Windows message WM_INITMENUPOPUP.
From the description of said message i think this is done every time
the menu becomes visible; the idea being that it can be changed
immediately before becoming visible.
So i guess it should be three events, however ssa may be able to shed
more light on this.
Kind regards, pl
Pavel Janík wrote:
Hi,
when implementing native menus, do I have to send SALEVENT_MENUACTIVATE
event before *every* opening of the menu, or is it enough to send this
event only the first time in "menu tracking sessions"? It should be enough,
but better ask ;-)
Ie. if the user opens menu File, Edit and then File again, is it enough to
send *two* events of this type, one for the first File menu opening and the
second for the Edit menu opening, or do I have to send one more event also
for the second File menu opening?
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.
-- Author unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
