🚀 go-pugleaf

Eric Bennett (ericb@psu.edu) wrote:
:>  In article <3vm1ga$dua@bug.rahul.net> Bill Moyer <ttk@rahul.net> writes:


:>  >  Read the fellow's post.  OS/2 and Windows *can* do it *exactly* the
:>  >way MacOS does it.  If you click a menu and hold down the button, then
:>  >when you release the button the menu will disappear.  If you release
:>  >the button while over a menu entry, you will choose that menu entry.
:>  >Or you can do the other thing - click the menu and let it hang around
:>  >while you make your selection.

:>  I am using Windows right now.  I click on menu and immediately let go of the 
:>  mouse.  On the Mac it goes away, and on Windows it stays.  Why would I just 
:>  click on the menu and then let go of the mouse button immediately?  I don't 
:>  know; I guess I do it while scanning menus for commands.  It's just my 
:>  personal habit from using the Mac, and it gets annoying while I'm using 
:>  Windows.  Also, if you pull down the wrong menu, Windows needs an extra 
:>  click to get rid of it without selecting something (unless you have held the 
:>  mouse button down while looking at the menu, but I don't do that).  Before you 
:>  take this the wrong way, remember that I am not calling this some sort of 
:>  fatal flaw in Windows--I'm just wondering whether anything exists to change it.

As I understand it, windows has some of the same roots as Motif, a GUI 
toolkit for X-windows.  Motif menus behave in the same fashion.  I guess 
it is just a matter of style.  Personally, I like it because it makes it 
easier to negotiate submenus.  In any event, I don't think that feature 
can be turned of in win 3.1.

-e