Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!decwrl!adobe!asente
From: asente@adobe.com (Paul Asente)
Newsgroups: comp.windows.x
Subject: Re: problems setting colormaps for subwindows...
Message-ID: <5646@adobe.UUCP>
Date: 16 Aug 90 16:56:58 GMT
References: <9008150543.AA14118@bullwinkle.unm.edu>
Sender: news@adobe.COM
Organization: Adobe Systems Inc.
Lines: 24

The DS3100 you're using (and, indeed, most workstations out today) have only
one colormap.  If you have an application that uses three colormaps for three
different windows, only one of them will ever be active.  Window managers
only install colormaps for top level windows, they are completely oblivious
to inferior ones.  As a consequence, only your top level window is ever
getting its colormap installed.

Setting the colormap windows *is*, however, the right thing for you to be
doing, since it means that your application will display correctly if it ever
happens to run on a workstation that can support three colormaps.

With the ICCCM as it is, there's really no way for you to internally manage
your colormaps (for example, by installing the colormap of a subwindow when
the cursor enters it).  The most portable thing for you to do is to have each
widget tree (i.e. shell widget and all its non-popup children) use the same
colormap.  In other words, the children that have different colormaps should
each be in a separate popup tree.

If you absolutely need the behavior you specify, you'll probably have to
implement your own, non-ICCCM window manager.

	-paul asente

New address!	asente@adobe.com	...decwrl!adobe!asente