Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!bloom-beacon!ATHENA.MIT.EDU!bjaspan
From: bjaspan@ATHENA.MIT.EDU (Barr3y Jaspan)
Newsgroups: comp.windows.x
Subject: Being sure that a window is unmapped
Message-ID: <9007161734.AA19871@beeblebrox.MIT.EDU>
Date: 16 Jul 90 17:34:42 GMT
Sender: bjaspan@mit.edu
Organization: The Internet
Lines: 12


As I understand it, if a program wants to be *sure* that a window is
actually visible on the screen after an XMapWindow request, the
program should block until it gets an Expose (not MapNotify) event for
that window.

Is there a similar mechanism for unmapping?  Does an UnmapNotify
actually guarantee that window is not on the screen or does it just
mean the server will consider removing it sometime in the future?

Barr3y Jaspan, bjaspan@athena.mit.edu
Student Information Processing Board (SIPB)