<I><FONT COLOR="#663300"><I><FONT COLOR="#663300"><I><FONT COLOR="#663300">Owning an old CJ I know what a slant six is. But what is a "deep six"?</FONT></I>

Would the phrase "six feet under" be clearer?

For those who still don't get the idiom, it means to bury, or in effect, to kill something. That's what I've done with class-based menus - they are a cool idea, but dog-slow in practice. I now prefer to use the old-fashioned Menu Builder and .MPRs for my apps.

If there seems to be significant interest, I can go back and look over the mods which were necessary to accomplish this in Codebook. I believe I just added an application-level logical property, and had other parts of the code, such as toolbars, check that before assuming anything about the existence of menu objects. It could then be added as an option in the framework.

</FONT></I>

Much clearer, thank you. Well, if MPR's are the way, let's go that way, but after the years I got used to the menu classes, and found the idea excellent... but slow. Simply sorry there seems to be no way to speed things up in an OOP fashion.

Jose</FONT></I>

The menus fine if you don't have an extensive menu system. Even in an app with lots of menus the performance hit only comes when the app loads. If your app load time is acceptable then by all means, keep the OO menus. As for the app I'm working on, loading the menus is so slow that I have a seperate progress bar just to show the progress of the menus loading ;>.

Michael G. Emmons

<a href="mailto:MichaelE@flashcreative.com">MichaelE@flashcreative.com</a>

Senior Consultant

<a href="http://www.flashcreative.com" class="white" onmouseover="style.color='#00cc00'" onmouseout="style.color='#0000ff'" title="Flash Creative Management Web Site">Flash Creative Management</a>