Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!pterodactyl.cis.ohio-state.edu!zwicky
From: zwicky@pterodactyl.cis.ohio-state.edu (Elizabeth D Zwicky)
Newsgroups: comp.windows.news
Subject: Re: Things That Won't Go Away
Message-ID: <43340@tut.cis.ohio-state.edu>
Date: 13 Apr 89 21:54:02 GMT
References: <41513@tut.cis.ohio-state.edu>
Sender: news@tut.cis.ohio-state.edu
Reply-To: Elizabeth D Zwicky <zwicky@cis.ohio-state.edu>
Organization: Ohio State University Computer and Information Science
Lines: 22

Here are the proven fixes for my problems (by popular request):

The immortal window with the item in it (which is, indeed, the one
from wallpaper), can be made mortal by putting *anything* on the stack
before the "itemdict forkitems" (I am using "(Food for Randomness)").
Neither I nor Phillip Nicholson, who sent me this answer, has any idea
why. Although the immortality surely must be due to a remaining
reference (as many, many people suggested), I had no luck in finding
one, and cannot conjecture why this fix would cause one not to be
created.

The visible but unmapped items are a result of items being
transparent. Mapping and unmapping transparent items does not
propagate damage to the parent canvas. Making /Transparent false in
/ItemCanvas makes it work beautifully. This was also suggested by
several people.

Send me mail if you would like the fixed version of wallpaper; it
should function identically to the unaided eye, but it doesn't leave
things around using memory when it goes away.

	Elizabeth Zwicky (zwicky@cis.ohio-state.edu)