Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!SUN.COM!dshr
From: dshr@SUN.COM (David Rosenthal)
Newsgroups: comp.windows.x
Subject: Re: problem with colormap (X11)
Message-ID: <8910271708.AA00388@devnull.sun.com>
Date: 27 Oct 89 16:59:32 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 30


> >> I create a private colormap for a specific window as follows:
> 
> >>    my_cmap = XCreateColormap(display, win, visual, AllocAll);
> >>    XSetWindowColormap(dipaly, win, my_cmap);
> 
> > This notifies the window manager that this window should have your
> > private colormap installed when the window gets the input focus.
> 
> Oops, is it not permitted for the window manager to separate keyboard
> focus from colormap focus?
> 
Please read sections 4.1.2.8, 4.1.8 and 4.2.6 of the ICCCM.  The policies that
window managers enforce for keyboard focus and colormap installation
have no neccessary relationship to one another.

Clients should set the ID of each sub-window that they expect to have
a colormap that is different from the top-level window's colormap in
a property called WM_COLORMAP_WINDOWS on the top-level window.  The
order of these windows is significant - the earlier in the list the
more likely the colormap is to be installed.

Clients should then set the colormap attribute of the sub-windows.
The window manager will notice these changes,  and when it decides
that the top-level window deserves to have its colormap(s) installed.
will install the first colormap(s) from the list.  The decision that
the window deserves to have its maps installed is up to the WM - it
may or may not have anything to do with the input focus.

	David.