Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!spdcc!tauxersvilli!alphalpha!nazgul
From: nazgul@alphalpha.com (Kee Hinckley)
Newsgroups: comp.windows.x
Subject: Re: Apparent limitation to WM_COLORMAP_WINDOWS?
Message-ID: <1991Apr27.143809.12676@alphalpha.com>
Date: 27 Apr 91 14:38:09 GMT
References: <9104260321.AA20403@zia.aoc.nrao.edu>
Organization: asi
Lines: 30

In article <9104260321.AA20403@zia.aoc.nrao.edu> cflatter@zia.aoc.nrao.EDU (Chris Flatters) writes:
>parent.  If you want the subwindow colormap to be installed only when
>the focus is in the subwindow you should set the list to
>
>	<parent, subwindow>
>
>and change the order in the list when your client detects that the subwindow
>has the focus; the window manager should watch for WM_COLORMAP_WINDOWS being
>changed and act on it.  
This is probably what you usually want.

>I am fairly certain that twm supports WM_COLORMAP_WINDOWS correctly.
When I make the call
    XtSetWMColormapWindows(shell, &widget, 1);
tvtwm crashes.  I've looked at its code for handling that stuff and
it may not be broke, but it's definite baroque.

    Line 2564 in events.c, where it says
	if (cmap->state & CM_INSTALL) {
    cmap is an invalid pointer.

Am I doing something wrong, or is it?
-- 
Alfalfa Software, Inc.          |       Poste:  The EMail for Unix
nazgul@alfalfa.com              |       Send Anything... Anywhere
617/646-7703 (voice/fax)        |       info@alfalfa.com

I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.