Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!gdavis
From: gdavis@primate.wisc.edu (Gary Davis)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Dialog interface (was Re: Movable-Modal WDEF 1.01 (LONG))
Message-ID: <1858@uakari.primate.wisc.edu>
Date: 9 Mar 90 22:08:59 GMT
References: <16589@well.sf.ca.us>
Sender: news@primate.wisc.edu
Reply-To: gdavis@primate.wisc.edu
Lines: 20

From article <16589@well.sf.ca.us>, by svc@well.sf.ca.us (Leonard Rosenthol):
>>
- 	Actually in his new product, Dialog Power (part of QuickTools), what
- Andrew has done is to adopt a method similar to that of MSWindows for showing
- the user what cmdKey will choose that button (or radio button or check box) 
- by underlining the letter in the title of the button that is the cmdKey equiv.
- (it's even in red on a CQD machine ;-)  I personally prefer this to the Nisus
- method since the contents of my buttons don't change just because I held down
- a modifier key.  I think that the Nisus method is a conceptually nice step,
- but a _BAD VISUAL_ one.  I also don't think that the Windows/DialogPower 
- method is perfect, but it's better.

I've always thought that those underlines all over the place in
Windows was one of the uglier aspects of that interface. The nice
thing about the Nisus method is that the command key equivalents
don't clutter things up unless you want to see them. Incidently,
the equivalent display doesn't change the contents of the button,
but puts up the reminder along side it.

Gary Davis