Path: utzoo!attcan!uunet!mcvax!guido From: guido@cwi.nl (Guido van Rossum) Newsgroups: comp.windows.x Subject: Re: single-window menus (was Re: twm reactions) Message-ID: <378@piring.cwi.nl> Date: 20 Jun 88 22:25:20 GMT References: <8806161258.AA00564@peewee.ux_kernel.com> Reply-To: guido@cwi.nl (Guido van Rossum) Organization: The Royal Society for Prevention of Cruelty to Amoebae Lines: 26 In article <8806161258.AA00564@peewee.ux_kernel.com>writes: >I am curious; would your menu system, as currently implemented, handle >the menu interaction style of: click to bring up menus, traverse the >menu items, then click on an item. The menu then disappears. > >Since you track *button* motion events, apparently your system >requires that the menu button be held down to bring up the menus, >traverse and then select by releasing the button on the item. I don't do this at the moment (I'm sticking dangerously close to the Macintosh design), but wouldn't it be possible by tracking pointer motion events while the menu window is popped up, possibly in combination with grabbing the mouse? (Uhh, I don't even know off-hand whether it's possible to do an active grab with no mouse buttons down.) Or, alternatively, if I don't need to provide highlighting feedback while no buttons are down, it would be even simpler (just don't unmap the window at the first button-up). I haven't tried the RTL menu package. My ideal menu package should have a way to turn a pop-up menu into a (temporary) static menu, e.g., by double-clicking on the title bar or some modifier-key. With the current state-of-the-art slow cheap workstations (aka VS2K) popping up the same menu to change three options is really tedious. -- Guido van Rossum, Centre for Mathematics and Computer Science (CWI), Amsterdam guido@piring.cwi.nl or mcvax!piring!guido or guido%piring.cwi.nl@uunet.uu.net