Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!bcm!etaylor
From: etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor)
Newsgroups: comp.windows.x
Subject: Re: bizarre behaviour???
Message-ID: <3103@gazette.bcm.tmc.edu>
Date: 6 Dec 90 22:28:32 GMT
References: <1990Dec6.201917.11507@thyme.jpl.nasa.gov>
Sender: usenet@bcm.tmc.edu
Reply-To: etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor)
Organization: Baylor College of Medicine, Houston, Tx
Lines: 29
Nntp-Posting-Host: wilkins.iaims.bcm.tmc.edu


|> If I change if from an InputOnly window to an InputOutput window, (yes,
|> I know that a depth of 0 on an InputOutput means CopyFromParent) then,
|> rather than seeing what's on the parent, I get a "hole" through my
|> application and can see whatever was underneath when the expose event
|> was received, e.g. root window root-weave, other applications, etc.
|> (note that what is displayed "underneath" does not change until another
|> expose event is received.)
|> 
|> I'd like to have a transparent InputOutput window.  I've looked through
|> the Server dix code for CreateWindow, but alas, I don't see anything
|> that looks relevent.  The above described behaviour seems odd to me; I'm 
|> reluctant to call it a bug though.

This is not a bug. 

A Window without a background is initialized to
whatever was behind it when it was mapped (usually).
I imagine the contents are just plain undefined.

If you don't have a background, something has to go there.

Notice that when you move it around, it keeps the original
contents.
--
					Eric Taylor
					Baylor College of Medicine
					etaylor@wilkins.bcm.tmc.edu
					(713) 798-3776