Path: utzoo!attcan!uunet!mailrus!ncar!boulder!devin
From: devin@boulder.Colorado.EDU (Yampalimardilor)
Newsgroups: comp.windows.x
Subject: Re: Another TWM colormap problem: ximage
Message-ID: <17654@boulder.Colorado.EDU>
Date: 2 Mar 90 16:39:50 GMT
References: <50525@lll-winken.LLNL.GOV> <50571@lll-winken.LLNL.GOV>
Sender: news@boulder.Colorado.EDU
Reply-To: devin@boulder.Colorado.EDU (Yampalimardilor)
Organization: University of Colorado, Boulder
Lines: 23

In article <50571@lll-winken.LLNL.GOV> jac@muslix.llnl.gov.UUCP (James Crotinger) writes:
!
!  Dennis O'Neill sent me a copy of a recently posted patch to
!TWM's menu.c which fixed a problem with colormap handling, but it
!didn't seem to make any difference as far as XImage or xlock are
!concerned. After installing the patched TWM I restarted X and
!immediately tried running XImage (without touching any menus, etc..),
!but no-go. If it's any help, when I run XImage, I get messages like:
!
!  twm:  client illegally changed colormap (i = -1, j = -1
!  twm:  client illegally changed colormap (i = -1, j = 0
!  twm:  client illegally changed colormap (i = -1, j = 0
!  twm:  client illegally changed colormap (i = -1, j = 0
!
!I get a similar message when I run xlock. So are xlock and XImage
!broken, or is it TWM. If it's not TWM, then why does this work OK
!with GWM. 

	I have a similar problem in my own code when running under R4 twm.
I am NOT doing a XInstallColormap.  I am doing an XSetColormap.  The error
is identical to the second error message above.  Any help would
be appreciated.  Thanks.
			-Devin