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: <38.26037AF7@imagery.FIDONET.ORG>
Date: 16 Mar 90 23:32:47 GMT
Sender: ufgate@imagery.FIDONET.ORG (newsout1.26)
Organization: FidoNet node 1:282/22.5 - Macintosh SmorgasBo, Bloomington MN
Lines: 17


 >>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!

Sorry, I must have misunderstood what you were saying (it was the end of a long day and I vaguely recall thinking you were asking for examples of where they were used rather than the more important question of when should you use modal dialogs.

Generally I agree with you completely, particularly for dialogs like the page set up.  I am less sure for the print dialog.  It is not presented until you have asked for a print (a non-modal request).  For the print to proceed, certain information is necessary.  For the application to process the print request, it either must ask for this information modally or assume that values established previously are still valid.  I'm having trouble picturing how a non-modal dialog presented when the "Print" menu cho


ice is selected would work.  Similarly, file dialogs which are only presented after you have asked the application to do something which requires this information.  My point is that there are times when going modal makes sense.

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