Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: Setting a new colormap
Message-ID: <8911151425.AA19101@expire.lcs.mit.edu>
Date: 15 Nov 89 14:25:13 GMT
References: <8911142132.AA10356@expo.lcs.mit.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 25


    From the ICCCM (and other sources)
    it sounds like I'm supposed to do the following.

Right.

    But what about XSetStandardColormap?

You can call this.

    What about XSetWindowColormap?

This is just a convenience interface to XChangeWindowAttributes, it's fine.

    Is there any way to request that a new colormap
    be installed for all of a client's windows without explicitly calling
    XChangeWindowAttributes for each window?

The theory is that most of the time you can do all of your colormap allocation
before you actually create the windows, in which case you avoid having to
run around and re-set all of your windows.  If not, there are probably a fair
number of systems under which just changing the colormap of your top-level
window (and not using WM_COLORMAP_WINDOWS) will cause the right display effect,
but it would be unwise to count on this behaviour.  You should really make sure
the colormap for each window is correct.