> The first thing I noticed was that the downloaded document had > Window2 as a Document. Changing it to a floating window replicated your situation.
The steps in the project are to switch frames back and forth to demonstrate the menu failures are caused by the floating window frame. I updated the project to properly start as a floating window so none else gets confused. > If you put the menuhandler in the app subclass it will work. This does not work for menus you only want activated when the floating window is activated. > I don't think it's a bug but one of the facts of floating windows. I wondered this too. But the docs indicate otherwise (see the last sentence in the note): Window.MenuBar ... Notes On Windows and Linux, a window can have a menubar just below its Title bar. It uses the menubar assigned to the window or the application's menubar if no menubar is assigned to the window. If it is a Windows MDI application, the MDI window uses the Application's menubar. Individual document windows cannot have a menubar, but this is due to a limitation built into Windows. However, floating windows can have a menubar, and those windows will display the menubar you specify for them. > Terry _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
