Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!muslix.llnl.gov!jac
From: jac@muslix.llnl.gov (James Crotinger)
Newsgroups: comp.windows.x
Subject: Re: Another TWM colormap problem: ximage
Message-ID: <50571@lll-winken.LLNL.GOV>
Date: 1 Mar 90 23:05:45 GMT
References: <50525@lll-winken.LLNL.GOV>
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: jac@muslix.llnl.gov.UUCP (James Crotinger)
Organization: Lawrence Livermore National Laboratory/UC Davis
Lines: 16


  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.