>To all,
>
>I have a form property that contains the name of a menu MPR file to run by DO mymenu.mpr when the form is activated. This menu file is set up to append a single menu pad onto the current system menu bar.
>
>When the form is deactivated, I release the extra PAD from the menu bar and if the form that is bring brought forward has a menu specified in its menu property, it will run in the same fashion.
>
>I was under the impression that DOing a menu this way would simply tag a menu PAD and RELEASE PAD later would effectively remove it. However, frequent, continued activating and deativating of forms with form-specific menu pads resulted in a serious performance drop.
>
>Is DOing the menu mpr likely to cause this ? If so, how should I change my strategy to have form-specific menus without perform degradation ?
>
>Tks,
>Carl Chambers
>Cardol Data Systems
I use a similar technique and have never noticed any performance penalty. The only thing that comes to mind would be to look at your code and see if maybe there's a PUSH MENU without a matching POP MENU. If the stack got very large perhaps performance could be impacted.
Also, you could inspect the generated code in the MPR and see exactly what's being done when you run that menu.
Rick Borup, MCSD
recursion (rE-kur'-shun) n.
see recursion.