jac@muslix.llnl.gov (James Crotinger) (03/02/90)
I'm trying to use XImage from NCSA under R4 and TWM. XImage is supposed to set up its own colormap. This does not seem to work worth beans when I run it under TWM. When I move my mouse into the window, there is a flash and for an instant the correct colors are displayed, but then it changes back to the default colormap. The behavior has tended to be a bit unpredictable. Under the original R4 release, occaisionally it would work correctly, and sometimes if it didn't, having TWM reread the .twmrc file would fix it. Since installing the latest version of R4 (both MIT patches and the LLNL patches), the unpredictability has dissipeared: it doesn't work every time 8-). When I run GWM with R4, or pswm with OpenWindows, things work fine. Also, when I have TWM reread the .twmrc file, things work fine for the short amount of time that there is no window-manager running. Has anybody else seen this? Any remedies? Thanks. Jim
jac@muslix.llnl.gov (James Crotinger) (03/02/90)
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.
devin@boulder.Colorado.EDU (Yampalimardilor) (03/03/90)
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