[comp.windows.x] twm xview colormap problem

johns@delilah.ccsf.caltech.edu (John Salmon) (09/05/90)

When using twm on a Sparcstation with Sun's Xview server, 
some (many?) of the XVIEW programs cause twm to print
the following warning:
twm:  client illegally changed colormap (i = 0, j = -1

Is this a twm bug, an Xview bug, or a "feature" of the
News/X common server?
Is it anything to worry about?

Thanks,
-- 
John Salmon		 Internet: johns@delilah.ccsf.caltech.edu
356-48 Caltech		 UUCP: johns%delilah.ccsf.caltech.edu@uunet.uu.net
Pasadena, CA 91125 USA	 Bitnet: johns@caltech.bitnet
			 delilah.ccsf.caltech.edu=[131.215.145.137]

cflatter@ZIA.AOC.NRAO.EDU (Chris Flatters) (09/06/90)

> When using twm on a Sparcstation with Sun's Xview server, 
> some (many?) of the XVIEW programs cause twm to print
> the following warning:
> twm:  client illegally changed colormap (i = 0, j = -1

Is this the X11R4 release of twm or the X11R3 version. The X11R4 release of
twm doesn't like clients installing their own colormaps: it is a violation of
the ICCCM.  If you try it twm will issue a message similar to the above
and reinstall the default colormap.

The XView clients should not need to install colormaps if X11R4 support
is present; indeed an nm and grep of the XView and OLIT libraries
(OpenWindows 2.0) did not pick up any uses of XInstallColormap.

It is possible that XView needs to use XInstallColormap to install colormaps
on subwindows if PRE_R4_ICCCM is defined at compile time (one of the drafts
of the ICCCM suggested that clients do this).  I have no way of checking this
at the moment since the source for the relevant function seems to be
missing from the xview2 distribution (sigh!).  Is it possible that you are
using an X11R4 twm on an older X11/NeWS server (OpenWindows 1.0.1)?   I
think that the OpenWindows 1.0.1 XView programs are probably pre-R4 ICCCM
versions (I seem to remember that OpenWindows 1.x was X11R3).

			Chris Flatters