Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!news.funet.fi!fuug!kth.se!cyklop.nada.kth.se!d88-jwa
From: d88-jwa@nada.kth.se (Jon W{tte)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Common (fatal) problem with DialogManager plus a solution
Message-ID: <1991Jan16.180013.13703@nada.kth.se>
Date: 16 Jan 91 18:00:13 GMT
References: <1991Jan2.073359.12067@uniwa.uwa.oz> <47962@apple.Apple.COM> <1991Jan11.002919.12966@dartvax.dartmouth.edu> <1991Jan15.191809.18212@pixar.uucp>
Distribution: comp
Organization: Royal Institute of Technology, Stockholm, Sweden
Lines: 19

In article <1991Jan15.191809.18212@pixar.uucp> upstill@pixar.uucp (It is not enough to win; others must lose. -- G. Vidal) writes:

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

Plus the DITL, plus any dctb and cicn and ICON and PICT and ... that
might be in the dialog. Don't forget the CDEFs that might be used.

I've adopted the practice "If the user deletes resources, too bad."

If the user doesn't insert the disk... well... don't everybody have
hard disks these days ? :-)

							h+
-- 

Jon W{tte, Stockholm, Sweden, h+@nada.kth.se