Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!mintaka!mit-eddie!bu-cs!dartvax!eleazar.dartmouth.edu!earleh
From: earleh@eleazar.dartmouth.edu (Earle R. Horton)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Modeless editText doesn't deactivate on suspend event
Message-ID: <17985@dartvax.Dartmouth.EDU>
Date: 19 Dec 89 21:35:42 GMT
References: <4448@hydra.gatech.EDU>
Sender: news@dartvax.Dartmouth.EDU
Reply-To: earleh@eleazar.dartmouth.edu (Earle R. Horton)
Organization: Dartmouth College, Hanover, NH
Lines: 16

In article <4448@hydra.gatech.EDU> cc100aa@prism.gatech.EDU
	(Ray Spalding) writes:
...
>It looks like DialogSelect is not multifinder friendly; shouldn't it
>TEDeactivate the editText item when it gets a suspend event?

One would think that this would be appropriate behavior.  DialogSelect
ignores suspend/resume events, however, and you have to handle them
yourself.  Probably the best approach is to change the event from an
app4Evt to an activateEvt, and set the modifiers, etc. so that DialogSelect
will do the right thing.  Note that this problem will also affect anything
else you may happend to have in a modeless dialog that needs to be
(de)activated when a suspend/resume event occurs.  Scroll bars come to
mind.

Earle R. Horton