Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!think!bloom-beacon!apple!tecot
From: tecot@Apple.COM (Ed Tecot)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MultiFinder and the event mask
Message-ID: <16353@apple.Apple.COM>
Date: 30 Aug 88 21:17:49 GMT
References: <3469@polya.Stanford.EDU> <15452@apple.Apple.COM> <32058@cca.CCA.COM>
Reply-To: tecot@apple.com.UUCP (Ed Tecot)
Organization: Apple Computer Inc, Cupertino, CA
Lines: 23

In article <32058@cca.CCA.COM> dee@CCA.CCA.COM (Donald Eastlake) writes:
>In article <15452@apple.Apple.COM> tecot@apple.com.UUCP (Ed Tecot) writes:
>>However, to answer your question, MultiFinder does not switch the system
>>event mask for each application.  Chances are that the application you launch
>>sets the system event mask itself.
>
>This sounds like nonsense to me.

You're right.  The above statement was wrong.  After checking a little
further, I found out that MultiFinder DOES in fact switch the event mask.
I responded with the way I thought it should work as opposed to the way
it does.

>(If you are claiming that events in the system event queue are the
>property of the "system" until an application actually senses them with
>Get/Wait/Avail then applications should also refrain from ever doing a
>FlushEvents, at least under MultiFinder (oops, I forgot you are never
>supposed to check if you are under MultiFinder.  I guess you are supposed
>to check the "system owns the system event queue" service ....))

How did you handle desk accessories prior to MultiFinder?  What's to stop them
from changing the system event mask?

						_emt