Path: utzoo!attcan!uunet!husc6!bloom-beacon!FARADAY.ECE.CMU.EDU!Dan.Nydick
From: Dan.Nydick@FARADAY.ECE.CMU.EDU
Newsgroups: comp.windows.x
Subject: widget with colormap
Message-ID: <8903281206.AA23640@faraday.ece.cmu.edu>
Date: 28 Mar 89 12:06:23 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 17


    I've written a widget which maintains its own colormap.  Things work OK
except for interactions with the various window managers (awm, uwm, twm).
First of all, none of the window managers will install my widget's colormap
automatically---I'm assuming this is because the widget's window is a
sub-window of a shell widget, and not directly controlled by the
windowmanager.  My solution to this problem was to bind an action to the
<EnterWindow> and <LeaveWindow> actions, one which calls XInstallColormap
and the other which calls XUninstallColormap.  This works fine running
awm or no wm at all, but twm or uwm see my widget fooling with the colormap
and promptly switch it back.
    The questions:
	1) Did I miss the "right" way of doing this?  (ie: should
		my widget really be calling XInstallColormap?)
	2) If my widget is supposed to call XInstallColormap, how do I
		tell the window managers not to instantly switch the
		colormap back?