Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!usc!bloom-beacon!bu-cs!dartvax!eleazar.dartmouth.edu!matthews
From: matthews@eleazar.dartmouth.edu (Jim Matthews)
Newsgroups: comp.sys.mac.programmer
Subject: Re: DA loses resource file on accRun
Keywords: MultiFinder DAs context switches
Message-ID: <14573@dartvax.Dartmouth.EDU>
Date: 21 Jul 89 15:04:42 GMT
References: <1989Jul17.045641.20314@lth.se> <2932@internal.Apple.COM>
Sender: news@dartvax.Dartmouth.EDU
Reply-To: matthews@eleazar.dartmouth.edu (Jim Matthews)
Organization: Dartmouth College, Hanover, NH
Lines: 18

In article <2932@internal.Apple.COM> goldman@apple.com (Phil Goldman) writes:
> The resource file was originally opened when the DA
>Handler was running.  However, at accRun time some other app may be 
>running, and that app has a different resource chain than DA Handler, so 
>when the resource manager searches the current chain it never does find 
>your map.

This is one more way in which MultiFinder makes DAs second class
citizens.  A more dramatic example of the problem can be seen by having
a DA open a window at accRun time -- it will appear in the foreground
app's layer, not (necessarily) the DA Handler's.

So, how hard would it be to make MultiFinder treat background DAs the
way it treats background apps -- i.e. do a minor switch to DA Handler
before issuing the accRun call?

Jim Matthews
Dartmouth Software Development