Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!agate!shelby!rutgers!njin!uupsi!pixar!upstill
From: upstill@pixar.uucp (It is not enough to win; others must lose. -- G. Vidal)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Common (fatal) problem with DialogManager plus a solution
Message-ID: <1991Jan15.191809.18212@pixar.uucp>
Date: 15 Jan 91 19:18:09 GMT
References: <1991Jan2.073359.12067@uniwa.uwa.oz> <47962@apple.Apple.COM> <1991Jan11.002919.12966@dartvax.dartmouth.edu>
Sender: news@pixar.uucp
Distribution: comp
Organization: Pixar -- Point Richmond, California
Lines: 9
Nntp-Posting-Host: valkyrie

If the problem is that the user refuses to offer up the disk with the
dialog on it, then I don't see why it's necessary to load ALL the
resources associated with the dialog (assuming that they're all on 
the same file).  If I just get, say, the DLOG via the Resource Manager
then IMMEDIATELY do the NewDialog call, the user has no chance to
eject the disk and deny me access to the remaining resources, 
nes c'est pas?  Sounds like a 90% solution to me.

Steve