🚀 go-pugleaf

In article <97@gilroy.dec.com> mikey@decwrl.dec.com (Mike Yang) writes:
[...]
>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.
I fixed my version to not install color maps, and to instruct the window
manager to do it (I use twm right now).  However the colormap *STILL* doesn't
look right.  The qix is made of the colors allocated by the other clients,
half of which are black.  The code seems to make a HSB map for the qix but
I have never seen it.  Life and hop (the fractals) also seem to suffer from
an overabundance of black.  I am shure twm installs my colormap, I set the
ColormapChangeMask bit so I could get colormap notify events.  I recieve one
on the xlock window for the cmap that xlock creates, and I never see it get
uninstalled.  So something strange is up with colormaps, do I not only have
to tell twm to install my map, but that I changed it?  That doesn't seem
right...
-- 
           stripes@wam.umd.edu          "Security for Unix is like
      Josh_Osborne@Real_World,The          Mutitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
    Who needs friends when you can sit alone in your room and drink?