>>You can use *skip for myproc* and arrange your popup as needed.
>>Cetin
>
>Cetin, that still doesn't quite work. If you put SKIP FOR in the DEFINE PAD command, the SKIP FOR is only executed at the time the menu is activated or when the pad is initially defined. The SKIP FOR is *not* executed every time the popup is activated. I need the capability to dynamically add and remove bars from the popup every time the popup is activated.
>
>Jim Booth's suggestion is the only way I know to accomplish this, but it can become quite convoluted when you have snippets of code all over the place that are altering a popup based on changes in the environment. I would much rather have the equivalent of a "BeforePopping" event for a popup. With this capabilitiy, I can have one snippet of code that uses current environment information (within my app) to set / remove all bars in the popup... i.e., exactly as one can do with a shortcut menu.
Mark,

You are incorrect, if you make the skip for in the menu definition a logical expression like;

DEFINE BAR 1 OF MyPop PROMPT "Something" SKIP FOR llDisSomething

then all you have to do is put this code to disable the menu item;

llDisSomething = .T.

and to reenable it;

llDisSomething = .F.