Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!att!ihlpf!spock
From: spock@ihlpf.ATT.COM (Weiss)
Newsgroups: comp.windows.news
Subject: Re: references, references, where are those references
Message-ID: <8700@ihlpf.ATT.COM>
Date: 6 Jun 89 22:04:45 GMT
References: <8671@ihlpf.ATT.COM>
Reply-To: spock@ihlpf.UUCP (Ed-Weiss)
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 23

I previously posted an article under this subject that described
a problem with creating a process from a window.  One thing I learned
is that if you want the process to live past the death of the
window, you have to put it in its own process group (/destroy of a
window does a killprocessgroup).  The real problem that I am having
is that when this process does live past the death of the window,
the process somehow keeps a reference to the window (so the canvases
are not garbage collected [and don't get removed from the screen if
they are mapped]).

Well it appears that my problem is that when you fork a process
it gets a copy of its parent's /SendContexts.  Why this happens, I
have no idea.  It seems to me that the child's /SendContext should
just be the current object.  Am I missing something obvious?

If I try to modify the /SendContext I get a invaildaccess.  Which is
probably a good idea, except if it is wrong.  Has anyone else come
across this problem?  Any fix/workaround?
-- 

Ed Weiss	   "I thought it was generally accepted, sir, that
att!ihlpf!spock     vulcans are an advanced and most honorable race."
		   "They are, they are.  And damn annoying at times."