Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!rutgers!mit-eddie!snorkelwacker!tut.cis.ohio-state.edu!att!cbnewsc!bwong
From: bwong@cbnewsc.ATT.COM (bruce.f.wong)
Newsgroups: comp.windows.news
Subject: Re: A dialog box class
Message-ID: <4529@cbnewsc.ATT.COM>
Date: 6 Nov 89 14:42:01 GMT
References: <8911032040.AA00674@tripoli.ees.anl.gov>
Reply-To: bwong@cbnewsc.ATT.COM (bruce.f.wong,55239,ihp,1a111,312 416 5111)
Organization: AT&T Bell Laboratories
Lines: 23

Can someone help me understand why /destroy is designed the way it is
in the Lite toolkit ?

	destroy in Dialog:

/destroy { DialogCanvas /Mapped false put currentprocess killprocessgroup } def

	DestroyClient, called by /destroy, in LiteWindow:

/DestroyClient { % - => - (Destroy client canvas &c.)
%	currentprocess killprocessgroup
	FrameEventMgr null ne {FrameEventMgr killprocessgroup} if
} def

o Why would you want to do a killprocessgroup instead of a killprocess ?
  A killprocess will get rid of the event manager for that window but a
  killprocessgroup will get rid of other unrelated event managers.

o In Dialog, why unmap the DialogCanvas ?
-- 
Bruce F. Wong		ATT Bell Laboratories
att!iexist!bwong	200 Park Plaza, Rm 1B-232
708-713-5111		Naperville, Ill 60566-7050