Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!ksand
From: ksand@Apple.COM (Kent Sandvik)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Application defined events in Multifinder
Message-ID: <49794@apple.Apple.COM>
Date: 2 Mar 91 01:56:22 GMT
References: <1991Feb23.140420.20707@ux1.cso.uiuc.edu> <25921@neptune.inf.ethz.ch>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 31

In article <25921@neptune.inf.ethz.ch> mneerach@iiic.ethz.ch writes:
>In article <1991Feb23.140420.20707@ux1.cso.uiuc.edu>, resnick@cogsci.uiuc.edu (Pete Resnick) writes:
>>I can't seem to find any documentation on this one. It appears that
>>PostEvent can be called at interrupt, so that I can post app1Evt's
>>from asynchronous completetion routines in my program to signal that
>>events have occurred. It is not clear, however, how I am to distinguish
>>my app1Evt's from those that might be posted by another application
>>running under Multifinder, or whether I will see these events at all
>>if I have been suspended. Is this documented somewhere, or does anyone
>>know what the story is?
>
>I don't know, but I believe Apple is discouraging developers from using
>appXEvt's for the purpose you described, since under extreme circumstances,
>events may be discarded. Maybe it's better to just set a boolean flag which
>is checked in the main event loop.

If one app send app1 events, and another app under MF sends app1 events,
and the events are sent to the *foremost* window, then everyone sees
the problem.

System7 with most structured IPC (or IAC in Apple terms) is the way
to go.

Regards,
Kent Sandvik


-- 
Kent Sandvik, Apple Computer Inc, Developer Technical Support
NET:ksand@apple.com, AppleLink: KSAND  DISCLAIMER: Private mumbo-jumbo
Zippy++ says: "C++ was given to mankind, so that we might learn patience"