Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!mit-eddie!bloom-beacon!EXPO.LCS.MIT.EDU!kit
From: kit@EXPO.LCS.MIT.EDU (Chris D. Peterson)
Newsgroups: comp.windows.x
Subject: Re: R4 Athena Widget question.
Message-ID: <9002281954.AA05118@expo.lcs.mit.edu>
Date: 28 Feb 90 19:54:21 GMT
References: <1990Feb26.192750.15430@agate.berkeley.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 23


> > me
> Frank
me

> > Since both the operating system and the X server are clever enough to free
> > up all resources associated with the client, it should be enough to just call
> > exit().  You can certainly be more clever, but it didn't seem worth putting a
> > bunch of code that doesn't accomplish anything into all the example programs.

> I think the important issue here is that application programmers don't know the
> contents or mechanisms of a widget. A widget writer is supossed to destroy
> everything that needs to be destroyed in the destroy callback.

After thinking about this some more I agree something else should be happening
here.  We will look into solving the problem.

						Chris D. Peterson     
						MIT X Consortium 

Net:	 kit@expo.lcs.mit.edu
Phone:   (617) 253 - 9608	
Address: MIT - Room NE43-213