Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cs.yale.edu!spolsky-joel
From: spolsky-joel@cs.yale.edu (Joel Spolsky)
Newsgroups: comp.windows.ms
Subject: Re: Need help w/Cascading Menus
Message-ID: <26017@cs.yale.edu>
Date: 5 Sep 90 22:13:17 GMT
References: <1990Sep5.192324.24707@rodan.acs.syr.edu>
Sender: news@cs.yale.edu
Organization: Yale University Computer Science Dept., New Haven, CT 06520-2158
Lines: 25
Nntp-Posting-Host: zoo-gw.cs.yale.edu
Originator: spolsky@suned.CS.Yale.Edu

In article <1990Sep5.192324.24707@rodan.acs.syr.edu> jfbruno@rodan.acs.syr.edu (John Bruno) writes:
|     +-----------+
|     | One      >|
|     |#Two######>+--------+
|     | Three     |Two-A   |
|     | Four      |Two-B##>+------+
|     +-----------|Two-C  >|More  |
|                 +--------|Stuff |  
|                          +------+
| 
| ...  I'd like to let the user select "Two-B" without
| having that third menu come up.  Will I have to write my own menu-handling
| beastie to do this?

What you are describing is not internally consistent. If the user
clicks and releases on the menu bar, then clicks and releases on Two,
what do you want to happen? You seem to be making the assumption that
the user will always drag the menus down, and never click. You are
also making the assumption that nobody uses the keyboard to select
items from menus. Both assumptions are wrong. Doing what you want
would be severly inconsistent with the SAA/CUA and make your users
unhappy. 

Joel Spolsky
spolsky@cs.yale.edu                                        Talk Hard.