Path: utzoo!utgpu!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: Things That Won't Go Away Message-ID: <41513@tut.cis.ohio-state.edu> Date: 3 Apr 89 21:50:43 GMT Sender: news@tut.cis.ohio-state.edu Reply-To: Organization: Ohio State University Computer and Information Science Lines: 25 Recently I've been having a horrible time making things go away in NeWS. First it was a window, created from another window, with a TextItem in it; it went away happily, unless the TextItem had been activated. As soon as that cursor started blinking, the window became immortal. After beating my head against that for a while, I simply cheated and unmapped the sucker in its /destroy. It still doesn't die, but it's at least invisible. Now, however, I have items that I am trying to make appear and disappear. I used to do this by adding a canvas to the item that was a child of the ItemCanvas, opaque, on top, and the same size, and mapping and unmapping this canvas. This works but is inelegant at best. It finally dawned upon me that I could just map and unmap the ItemCanvas. Wrong. I can map and paint it, and it appears, but after I unmap it it doesn't disappear until I repaint the parent window. The parent window has 20-odd items in it, and repainting it is unpleasant at best. The manual says a lot of things about the conditions necessary for a canvas to appear, but nothing about the conditions necessary for it to *dis*appear. I can just make do with the various hacks I've evolved, but it pains my aesthetic sense. Does anyone have any suggestions about less horrible ways to get around these problems? Elizabeth (zwicky@cis.ohio-state.edu)