Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!ucbvax!agate!usenet
From: welch@soda.berkeley.edu (Sean N. Welch)
Newsgroups: comp.windows.x
Subject: Re:  386i/OpenWindows 2.0/MIT Distrib Problems
Summary: How to get olwm to not be so picky about ICCCM compliance
Keywords: ICCCM olwm
Message-ID: <1991Jan2.021455.28989@agate.berkeley.edu>
Date: 2 Jan 91 02:14:55 GMT
References: <9101010632.AA27736@Larry.McRCIM.McGill.EDU> <8812@dog.ee.lbl.gov>
Sender: welch@soda.berkeley.edu
Organization: UC Berkeley, CS Undergraduate Association
Lines: 22


If you are using olwm from OpenWindows V.2 (and I may be wrong in
assuming that it performs the same way as the one I ftp'd off of 
expo) there should be a resource that can solve your problem with
non-ICCCM compliant clients.  Here's a clip from my .Xresources:

OpenWindows.FocusLenience:      true

And the clip from the man pages here:

     FocusLenience (boolean)
          If this is set to true, olwm will not enforce the ICCCM
          requirement that windows must have the input hint set
          in order to receive the input focus.  This option is
          useful if you run clients that aren't ICCCM-compliant,
          like many X11R3-based clients.  Default value: false.

You'll have to ask elsewhere if you are having the problem with 
another window manager.

Sean Welch
Computer Science Undergraduate Association, University of California, Berkeley