Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!xanth!ames!amdahl!oliveb!amiga!jimm
From: jimm@amiga.UUCP (Jim Mackraz)
Newsgroups: comp.sys.amiga.tech
Subject: Re: inputs from many windows.
Keywords: windows, messages, IDCMP, stupid!
Message-ID: <3304@amiga.UUCP>
Date: 3 Feb 89 19:04:54 GMT
References: <1918@pur-phy> <439@madnix.UUCP> <327@wn2.sci.kun.nl>
Reply-To: jimm@cloyd.UUCP (Jim Mackraz)
Distribution: comp.sys.amiga.tech
Organization: Commodore-Amiga Inc, Los Gatos CA
Lines: 26

In article <327@wn2.sci.kun.nl> janhen@wn2.sci.kun.nl (Jan Hendrikx) writes:
)By the way, the version of CloseWindowSafely() that I got here uses
)Forbit()/Permit() around its message Remove()ing loop.  What I say on
)the net uses LockIBase()/UnLockIBase(). Is that sufficient for the
)purpose (of making sure no new IntuiMessages are PutMsg()ed to the
)port)?

It is very incorrect.  Let me quote from the autodocs of LockIBase:

*       Grabs Intuition internal semaphore so that caller may examine
*       IntuitionBase safely.

This has nothing to do with messaging, nothing to do with millions of other
pretend uses of LockIBase().  We reserve the right to assume that uses of
LockIBase() are exactly as documented.

Apart from this, Olaf, your interpretation of ModifyIDCMP() was sound.

)-Olaf Seibert (using Jan's account)

	jimm
-- 
Jim Mackraz, I and I Computing	   	"Like you said when we crawled down
{cbmvax,well,oliveb}!amiga!jimm          from the trees: We're in transition."
							- Gang of Four
Opinions are my own.  Comments are not to be taken as Commodore official policy.