Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!ZIA.AOC.NRAO.EDU!cflatter
From: cflatter@ZIA.AOC.NRAO.EDU (Chris Flatters)
Newsgroups: comp.windows.x
Subject: Re:  Openwindows colormaps
Message-ID: <9009062103.AA03202@zia.aoc.nrao.edu>
Date: 6 Sep 90 21:03:00 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 28


Andrew Hunt writes:

>Whenever the cursor is moved over the workspace area, the default colormap
>is re-installed by the window manager (olwm).  
>
>This behavior makes it all but impossible to run a serious image processing
>application under Openwindows.  The only time the right colormap is 
>installed is when the cursor is actually over one of the application's
>windows.
>
>What I want the window manager to do is to leave my application's color
>map installed when the cursor is moved onto the workspace.  Motif
>Window Manager (mwm) seems to do this just fine, but I can't get olwm
>to behave in this way.

I run an image processing application under OpenWindows quite a bit of
the time and I find it quite reasonable that it behaves in the way it
does.  I also seem to recall that twm behaves in the same way.  The
rationale for this is presumably that other windows (and all of the
window decoration) may become invisible or indistinct while your image
colormap is installed and that you want to be able to see the other windows
when you aren't expressing an interest in your image (by placing your cursor
there).

If you really want the colormap to stay installed as you leave the window,
I think that you should be able to get the required behaviour by setting
the input area to click select in the workspace properties menu.