
Standard colormaps were spec'd with the intention that window managers
would make them available. This doesn't mean that every window manager
author in the world immediately dropped everything they were doing and
implemented this at top priority.

The ESGE server we ship makes the XA_RGB_BEST_MAP available at
startup. It doesn't wait for window managers to do it.


Does your hardware have only one CLUT? Since standard colormaps
typically devour all 256 entries, there is no way it can avoid
displacing the entire default colormap if your hardware has only one
CLUT.

I don't believe standard colormaps are intended to aboid possible
colormap flashing between clients using the default coilormap. Rather,
colormap flashing will be avoided between two clients that use the
same standard colormap. An example would be two clients that need a
full color range would both use XA_RGB_BEST_MAP (or whatever it's
called under X11R5).

If you are trying to avoid colormap flashing with the default
colormap, your best bet is to try to load all the colors you use into
that colormap. If you can't do that, then you'll get flashing on a one
hw CLUT framebuffer.

Now if your window manager used the same standard colormap as your
client, this flashing could also be avoided. Perhaps some window
managers have command line options for selecting standard colormaps?
-- 