We're currently working on a cross-platform application that installs its own system menu using the "installMenu" command. However, I've only just noticed this little addendum on the Macromedia support site (tech note ID: 16117) which states:
"Known Issues Frequent menu changes can result in a performance drain causing a menu to lose some of its functionality. For best results, avoid frequent menu changes including installing/removing menus and repeatedly changing menu item properties. A potential workaround to the performance drain is to remove and then reinstall the menu." Has anyone had any practical experience with this problem? How much of a "drain" are we talking about? How many changes are considered "frequent"!?! If anyone at MM is reading this, can you throw any extra light on the matter? Since in our app it's entirely possible that the user can cause the state of one of the menu items to toggle (between enabled and disabled) quite often - is the menu going to spontaneously combust after a while? Ta muchly, Chris ACTF [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
