Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!sol.ctr.columbia.edu!src.honeywell.com!msi.umn.edu!cs.umn.edu!ux.acs!vx.acs.umn.edu!dhoyt
From: dhoyt@vx.acs.umn.edu (David Hoyt)
Newsgroups: comp.sys.mac.programmer
Subject: MacApp model dialogs (was Re: Scrolling lists in dialogs)
Message-ID: <2896@ux.acs.umn.edu>
Date: 13 Dec 90 15:52:08 GMT
References: <2535@trlluna.trl.oz> <1990Dec11.144800.22863@midway.uchicago.edu> <5024@husc6.harvard.edu> <1990Dec13.090206.925@actrix.gen.nz>
Sender: news@ux.acs.umn.edu
Reply-To: dhoyt@vx.acs.umn.edu
Organization: University of Minnesota, Academic Computing Services
Lines: 11

In article <1990Dec13.090206.925@actrix.gen.nz>, Bruce.Hoult@bbs.actrix.gen.nz writes...
>You forgot *modeless* dialogs...  Er, and I think MacApp uses the standard
>mechanism for alerts.

  No, MacApp doesn't do clasical 'modal' dialogs at all (even for alerts),
but rather simulates them with windows.  If you compile with the qInspector
option you can test this by selecting the model/modeless options in the
Inspector menu.  This allows you to check the 'look and feel' of model vs.
modeless dialogs at runtime.

david | dhoyt@vx.acs.umn.edu | dhoyt@umnacvx.bitnet