Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unexpected warnings on Screen 2

4 views
Skip to first unread message

Charles Lindsey

unread,
Oct 16, 2007, 9:44:17 AM10/16/07
to
Back in the days when I was using Solaris 7 on a Sparc 5, I ran two screens.

0.0 was a bwtwo, and 0.1 was a cgsix, set up for Pseudocolor. Various
applications using motif, dt, xview ran fine on screen 1 with no problem.

Now I am using Solaris 10 on an Ultra 2, where 0.0 is the inbuilt creator
graphics (Truecolor, of course) and 0.1 is a cgsix using Pseudocolor.

Now, whenever I start an application such as dtpad, I get a Warning:

Warning: Cannot allocate colormap entry for "#D1D1C0C0AEAE"

and similar Warnings with XView applications such as cmdtool.

I have, of course, chosen some pretty colors with the Style Manager, which
gives rise, within ~/.dt/sessions/home/dt.resources, to

*0*ColorPalette: BeigeRose.dp
*0*ColorUse: DEFAULT
*1*ColorPalette: BeigeRose.dp
*1*ColorUse: DEFAULT
Window.Color.Background: #FFFFFFFFFFFF
Window.Color.Foreground: #000000000000
OpenWindows.WindowColor: #D1D1C0C0AEAE
OpenWindows.WindowForeground: #000000000000
OpenWindows.DataBackground: #FFFFFFFFFFFF
OpenWindows.DataForeground: #000000000000
OpenWindows.WorkspaceColor: #D1D1C0C0AEAE
*background: #D1D1C0C0AEAE
*foreground: #000000000000

(and in fact #D1D1C0C0AEAE is actually the 'beige' out of 'BeigeRose').

It seems that dtwm sets up a default Colormap with the first 22 entries
being read/write, and including (at least some of) the BeigeRose colors,
and in particular D1D1C0C0AEAE. The rest of the ColorMap is filled with
an assortment of, presumably useful, read-only colors (so the Colormap is
now full).

Then the application uses XAllocColor to find D1D1C0C0AEAE, but since
XAllocColor only returns existing colors if they are read-only, and the
Colormap is full so they cannot add it again, it returns Fail and puts out
that Warning message. Then, having failed to find a pixel for the color it
wants it goes looking for XtDefaultBackground (which is, of course,
D1D1C0C0AEAE, so what you see on the screen is exactly what you wanted to
see).

But how did this mess arise, and how can things be configured so those
warning messages do not appear?

--
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl
Email: c...@clerew.man.ac.uk Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

0 new messages