Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!cs.utexas.edu!ut-emx!jdm
From: jdm@ut-emx.UUCP (Jim Meiss)
Newsgroups: comp.sys.mac.programmer
Subject: Re: DA problem under Multifinder
Summary: Still a problem
Keywords: LSC, option key, DA Handler
Message-ID: <8328@ut-emx.UUCP>
Date: 29 Nov 88 23:51:53 GMT
References: <8268@ut-emx.UUCP> <7776@well.UUCP>
Reply-To: jdm@emx.UUCP (James Meiss)
Organization: UTexas Computation Center, Austin, Texas
Lines: 26

In article <7776@well.UUCP> wdh@well.UUCP (Bill Hofmann) writes:
>In article <8268@ut-emx.UUCP> jdm@ut-emx.UUCP (Jim Meiss) writes:
>>
>>	I'm perplexed about the some weird behavior
>>in a DA I'm writing using LSC 3.0. 
>
>As far as I know, the problem you describe is not your fault.  Here's
>what happens:
>1.	When you open a DA with the option down, the DA is opened
>	and the DCE entry FOR THE TOPMOST APPLICATION is filled.
>2.	When you open a DA without option, DA Handler takes care
>	of it (ie, MultiFinder checks to see whether it's launched,
....
>	In this case, the DCE in the DA Handler is filled.
	
	As far as I can tell, all the DCE's are contained in the system
heap. Thus multifinder should check there to see if a DA is currently opened
or not. I don't know how I can tell which application layer contains the
DA, but it seems to be able to, with most DA's. 
	My DA, created with LSC 3.0, seems to not be able to tell Multifinder
that its loaded into an application layer, and so Multifinder trys
to launch DA handler.
	Something is wrong with my code, or with LSC's DRVR code, because
other DA's don't have this problem....
					Jim Meiss
					jdm@emx.utexas.edu