Path: utzoo!censor!comspec!lethe!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!clyde.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!samsung!zaphod.mps.ohio-state.edu!wuarchive!mit-eddie!bloom-beacon!dont-send-mail-to-path-lines
From: gjw@spurr.wr.usgs.GOV (Gregory J. Woodhouse)
Newsgroups: comp.windows.x
Subject: Re:  resource ID allocation
Message-ID: <9102141954.AA15837@spurr.wr.usgs.gov>
Date: 14 Feb 91 19:54:02 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 12

What happens to a window if its parent is destroyed?  More precisely, is
the window ID freed, or does it turn into something akin to a zombie
process under Unix (but one that hangs around forever)?

Unless I'm misunderstanding the problem here, it seems that destroying
orphaned windows (after the process that created them exits or its
rootwindow is destroyed, of course) would solve your problem.

Gregory Woodhouse
U.S. Geological Survey
gjw@ags.wr.usgs.gov
(415) 329-4694