Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!ico!auto-trol!marbru
From: marbru@auto-trol.UUCP (Martin Brunecky)
Newsgroups: comp.windows.x
Subject: Re: (none)
Message-ID: <644@auto-trol.UUCP>
Date: 17 Jan 90 16:15:35 GMT
References: <900116092302.25200122@CCC.NMFECC.GOV>
Reply-To: marbru@auto-trol.com (Martin Brunecky)
Organization: Auto-trol Technology, Denver
Lines: 32

In article <900116092302.25200122@CCC.NMFECC.GOV> POTHIERS@TUVA.SAINET.MFENET writes:
>
>From the ICCCM I gather than I should set the WM_COLORMAP_WINDOWS property
>to the windows that need to have colormaps installed. My problem is that 
>I need to install this property on a window that the Window Manager 
>knows about. 
>
>In my application I create multiple "top level" windows that each need
>different colormaps. Each of these "top level" windows is tracked
>separately by the WM for colormap focus. Given a widget many levels down
>in a window how do I find the window that should contain the 
>WM_COLORMAP_WINDOWS property? 
>
	Using Xt, the top-level-shell is tracked by the WM, so you
	have to modify the WM_COLORMAP_WINDOWS property on the shell
	(giving the list of window-id's for subwindows of this shell
	which have the colormap attribute different).
	Now,
	you may run into problems with the default visual, which may
	not support your colormap (R3 Xt widgets inherit visual from
	the root window).
	Also, many R3 window managers do NOT handle WM_COLORMAP_WINDOWS
	property correctly: OSF/Motif 1.0 distribution of mwm, both
	DECwindows wm (VMS & Ultrix). However, those wm's usually
	install the "right" colomap if you set your colormap for the
	shell.

-- 
###############################################################################
Martin Brunecky, Auto-trol Technology Corporation,
12500 North Washington Street, Denver, CO-80241-2404
(303) 252-2499                                        ncar!ico!auto-trol!marbru