[comp.windows.x] DefaultColormap bug?

madd@adt.UUCP (jim frost) (01/11/89)

I'm not sure if it's a bug or not but I have noticed that it's
possible to delete the default colormap, at least on the Sun server.
This breaks just about all following programs that attempt to use
color (sunGetPixel: can't allocate pixel [or some such] gets written
on the console a lot and the client dies with an XError).

I've fixed this problem by not freeing a colormap if it matches that
returned by DefaultColormap() but I'm curious as to whether it's a
bug, a feature, or what.

Jim Frost
Associative Design Technology
madd@bu-it.bu.edu

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (01/12/89)

It's definitely a bug to be able to delete it.  The Protocol spec
is explicit on this (see FreeColormap; p. 422 in the Digital Press book).