Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!mikey
From: mikey@decwrl.dec.com (Mike Yang)
Newsgroups: comp.windows.x
Subject: Re: colormap problem with xlock
Keywords: xlock, twm, colormap
Message-ID: <97@gilroy.dec.com>
Date: 7 Feb 90 17:19:17 GMT
References: <17381@duke.cs.duke.edu>
Organization: DEC Western Software Lab
Lines: 25

In article <17381@duke.cs.duke.edu> ndd@macbeth.cs.duke.edu (Ned D. Danieley) writes:
>when a user on a 3/260CXP selects xlock, he gets the following
>error message:
>
>twm:  client illegally changed colormap (i = 0, j = -1
>
>xlock does lock the screen, but the patterns don't look right,
>and the qix display looks bad. this didn't happen under R3;
>any idea why it would with R4?

The problem is that xlock calls XInstallColormap itself, instead of
setting the colormap window attribute and letting the window manager
peform the installation, as the ICCCM states.

The version of twm shipped with R4 enforces this convention and
negates the installation by reinstalling the colormaps it wants
installed.  Therefore, the hardware colors are not as xlock expectes,
and this would explain why things "don't look right."

The solutions are to fix xlock to follow ICCCM conventions, or to use
a less restrictive window manager.

-----------------------------------------------------------------------------
Mike Yang	   Western Software Laboratory	Digital Equipment Corporation
mikey@wsl.dec.com	  decwrl!mikey			 415/853-6677