Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!decwrl!shelby!polya!kaufman From: kaufman@polya.Stanford.EDU (Marc T. Kaufman) Newsgroups: comp.sys.mac.programmer,comp.sys.mac Subject: Re: Checking for MF (was Re: Need some MF help) Message-ID: <8235@polya.Stanford.EDU> Date: 7 Apr 89 02:03:18 GMT References: <1179@internal.Apple.COM> <2749@pegasus.ATT.COM> <1234@internal.Apple.COM> Sender: Marc T. Kaufman Reply-To: kaufman@polya.Stanford.EDU (Marc T. Kaufman) Followup-To: comp.sys.mac.programmer Distribution: comp.sys.mac.programmer,comp.sys.mac Organization: Stanford University Lines: 18 Xref: utzoo comp.sys.mac.programmer:5428 comp.sys.mac:29664 In article <1234@internal.Apple.COM> goldman@apple.com (Phil Goldman) writes: >In article <2749@pegasus.ATT.COM> ech@pegasus.ATT.COM (Edward C Horvath) >writes: .> This works fine EXCEPT when the application is part of a "Set Startup" .> set and does not wind up frontmost. The app is set up in background, .> and stays in background, but doesn't receive an initial Resume OR .Suspend. >MF *does* give background apps a suspend event as the first event. >However, like all suspend/resume events the event will be dropped if the >app calls _WaitNextEvent/_GetNextEvent/EventAvail with app4 events masked >out. Perhaps this is why your app does not see it. Or perhape we are all calling GetNextEvent 4 times before actually looking at the event returned [I forget what this hack was for]? Or calling FlushEvents at the start of the App? Marc Kaufman (kaufman@polya.stanford.edu)