Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!imagery!p5.f22.n282.z1.FIDONET.ORG!Jim.Spencer
From: Jim.Spencer@p5.f22.n282.z1.FIDONET.ORG (Jim Spencer)
Newsgroups: comp.sys.mac.programmer
Subject: When to use a _real_ moda
Message-ID: <31.25FE3449@imagery.FIDONET.ORG>
Date: 13 Mar 90 05:42:18 GMT
Sender: ufgate@imagery.FIDONET.ORG (newsout1.26)
Organization: FidoNet node 1:282/22.5 - Macintosh SmorgasBo, Bloomington MN
Lines: 26


 >As I understand it, there are 4 kinds of dialogs:
 >
 >(a) an alert,
 >(b) a "real" modal dialog, i.e. a modal dialog that is too complex for
 >    the _Alert trap, and is _really_ modal,
 >(c) a "movable" modal dialog, i.e. a dialog that is modal with respect
 >    to the application, but modeless with respect to the rest of the
 >    world,
 >(d) a modeless dialog.
 >
 >Only in case (b) one should use _ModalDialog (again, as I understand it).
 >
 >Now, my question is:  Does case (b) ever occur in practice?  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.  Moreover, Alert() simply calls ModalDialog() to actually handle the alert's events.



--  
Jim Spencer - via FidoNet node 1:282/33
UUCP: ...!uunet!imagery!22.5!Jim.Spencer
ARPA: Jim.Spencer@p5.f22.n282.z1.FIDONET.ORG