Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!think!snorkelwacker!bloom-beacon!eru!luth!sunic!mcsun!hp4nl!fwi.uva.nl!kim!freek
From: freek@fwi.uva.nl (Freek Wiedijk)
Newsgroups: comp.sys.mac.programmer
Subject: Re: When to use a _real_ modal dialog
Message-ID: <529@fwi.uva.nl>
Date: 15 Mar 90 11:23:08 GMT
References: <31.25FE3449@imagery.FIDONET.ORG>
Sender: news@fwi.uva.nl
Reply-To: freek@fwi.uva.nl (Freek Wiedijk)
Organization: Faculteit Wiskunde & Informatica, Universiteit van Amsterdam
Lines: 18

In article <31.25FE3449@imagery.FIDONET.ORG>
Jim.Spencer@p5.f22.n282.z1.FIDONET.ORG (Jim Spencer) writes:
>
> >When one
> >uses a dialog of type (b), is it not _always_ bad interface design?  If
> >so, then what is the use of the _ModalDialog trap?
>
>You use type (b) Modal dialogs all the time.  For a couple of trivial
>examples, take a look at your page setup and print dialogs in any
>application.

BUT!  I consider the current way that page setup and print dialogs are
handled BAD interface design.  Why, fer gossake, should a page setup or
print dialog be modal?  Give me ONE reason!

--
Freek "the Pistol Major" Wiedijk                  Path: uunet!fwi.uva.nl!freek
#P:+/ = #+/P?*+/ = i<<*+/P?*+/ = +/i<<**P?*+/ = +/(i<<*P?)*+/ = +/+/(i<<*P?)**