> Also, it appears we allocate black and white as writeable colors; the
> GDK documentation says of the "writeable" argument to
> "gdk_colormap_alloc_color()":
>
> writeable : If TRUE, the color is allocated writeable (their
> values can later be changed using gdk_color_change()).
> Writeable colors cannot be shared between applications.
>
> but we don't ever change black or white with "gdk_color_change()".
Yeah, I should not have done that. I just spoke to my local gtk expert
who explained that writable was exactly wrong in this situation.
>
> "Writeable colors cannot be shared between applications." seems to imply
> that those colors might take more colormap space than non-writeable
> colors; a look at the actual GDK 1.2.4 code indicates that, if
> "writeable" is true, it'll allocate a colormap cell for the color, but
> that it may not do so for non-writeable colors.
This is true. There are also some servers which allocate only a few or
no entries in the colormap as writable so some servers may "always" fail
with this code...
>
> If the scarce resource is free colormap cells, allocating non-writeable
> colors, although it means we may have to settle for a color that's close
> to white or black, rather than getting Real White and Real Black, may
> keep us from colliding with color hogs.
True. It is amazing how much I have learned about gtk from this
effort. Phil, if you want to change the writable flags to false, please
do so. I'm a little snowed right now with some unexpected work...
--john
--
John McDermott jjm@xxxxxxxxxx
Writer and Computer Consultant
J-K International, Ltd.
+1 505/377-6293 - V
+1 505/377-6313 - F
