Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!AMD-26.HAC.COM!dhuff
From: dhuff@AMD-26.HAC.COM (Daryl Huff)
Newsgroups: comp.windows.x
Subject: transparent windows
Message-ID: <8909132250.AA02504@amd-26.hac.com>
Date: 13 Sep 89 22:50:15 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 16

> windows.  A better design is to create a new visual type (transparent
> static gray or whatever you have), create a trivial extension which returns
> the visualid of this new visual type, and the magic pixel value which
> makes it transparent, and then create windows using the new visual type.

I don't understand what you mean by "magic pixel value".  Let me explain
a bit more about what I hope to accomplish.  The system I am working on has
an 8 plane frame buffer.  I would like to be able to split the planes into
two or three groups.  For example I may want to split the 8 planes into two
groups of four planes each.  The first group of four planes would be used
to display windows with maps in them.  The second group of four planes could
 be used for menues, xterm windows, etc.  I want the map data to be 
visible "through" the menues, xterm windows, etc.  I want the cursor to give
positions relative to any window (map or xterm).  I also want separate
expose events for the two groups of planes.  (i.e. The map windows should
generate exposure events when a pop-up menu is brought up then taken away.)