Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!rpi!zaphod.mps.ohio-state.edu!menudo.uh.edu!sugar!peter From: peter@Sugar.NeoSoft.com (Peter da Silva) Newsgroups: comp.sys.amiga.advocacy Subject: Re: De-macification of the Amiga (Re: The Amiga's Future) Message-ID: <1991Jun27.115950.24857@Sugar.NeoSoft.com> Date: 27 Jun 91 11:59:50 GMT References: <1991Jun24.094738.29131@Sugar.NeoSoft.com> <14300@pasteur.Berkeley.EDU> Organization: Sugar Land Unix -- Houston, TX Lines: 28 In article lron@easy.lrcd.com (Dwight Hubbard) writes: > Good explanation, but you happen to have any Idea why the damn menus are in > screen title bar instead of the title bar for the window were they belong?? Because they don't belong either place. They should remain invisible until selected with the menu button, and pop up under the mouse with the last selected option already active. In article <14300@pasteur.Berkeley.EDU> navas@cory.Berkeley.EDU writes: > Benefits: (for clipping to window) > Only that window will have it's graphic rendering halted, no other > window would be affected, and other programs wouldn't appear to > "freeze" That's not a benefit of putting the menus in the window title bar. That's a benefit of drawing the menus through layers.library. You could do that with the current menu sysyem as well. It'd just slow them down a bit. > Problems: > The window may not be large enough to display the menu. No problem, just use scrolling menus. I suspect it'd be possible to write a handler like PopUpMenu that'd do the job. Go for it. -- Peter da Silva. `-_-' . 'U` "Have you hugged your wolf today?"