Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!comp.vuw.ac.nz!actrix!Bruce.Hoult
From: Bruce.Hoult@bbs.actrix.gen.nz
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacApp model dialogs (was Re: Scrolling lists in dialogs)
Message-ID: <1990Dec14.165910.27928@actrix.gen.nz>
Date: 14 Dec 90 16:59:10 GMT
References: <5024@husc6.harvard.edu> <1990Dec13.090206.925@actrix.gen.nz> <2896@ux.acs.umn.edu>
Sender: Bruce.Hoult@actrix.gen.nz (Bruce Hoult)
Organization: Actrix Information Exchange, Wellington, New Zealand
Lines: 23
Comment-To: dhoyt@vx.acs.umn.edu

In article <2896@ux.acs.umn.edu> dhoyt@vx.acs.umn.edu writes:
> 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

There are plenty of calls to StopAlert, CautionAlert etc in the MacApp
sources.

And your argument is circular:  you can't use the Inspector to play with
dialogs and alerts unless they are using uDialog instead of the Dialog
manager, so saying you can set the modal/modeless option is rather
pointless -- you *can't* do it for dialog manager stuff.
-- 
Bruce.Hoult@bbs.actrix.gen.nz   Twisted pair: +64 4 772 116
BIX: brucehoult                 Last Resort:  PO Box 4145 Wellington, NZ