Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!caen!sol.ctr.columbia.edu!spool.mu.edu!decwrl!csus.edu!ucdavis!csusac!unify!openlook!openlook-request From: openlook-request@openlook Newsgroups: comp.windows.open-look Subject: Re: ***!?! Help needed with re-use of Xview colourmaps !?!*** Message-ID: Date: 29 May 91 13:30:43 GMT Article-I.D.: openlook.vv7styw Lines: 39 > I have a base application which in turn executes (in turn) a number > of Xview applications. Each of these applications uses its own > (statically allocated) palette, and it is here that the problem > arises... If you're using olwm/olvwm, here's a section from the man page that might help: In color-locked mode, colormaps are not installed based on pointer motion. To enter color-locked mode, press the Color-Lock key over the window whose colormap you wish to install. When you press this key, the colormap of the eli- gible window under the pointer is installed into the hardware. You can move the pointer anywhere on the screen and this colormap will remain installed in the hardware. If you're already in color-locked mode, you can press the Color-Lock key over another window to install that window's colormap. Also... ColorFocusLocked (boolean) Specifies the initial state of the colormap focus pol- icy. If true, the default colormap is locked into the hardware. If false, the colormap of the window under the mouse is kept installed. Default value: false. ColorLockKey (key specification) Specifies the key that is used to lock the colormap focus. See the section on Colormap Installation for more details. Default: control-L2. ColorUnlockKey (key specification) Specifies the key that is used to unlock the colormap focus. See the section on Colormap Installation for more details. Default: control-L4. Hope this helps, Frank G.