Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!usc!ucsd!helios.ee.lbl.gov!epb2.lbl.gov!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.windows.x
Subject: Re: twm Doesn't Map Keyboard Input Correctly
Keywords: keyboard input, window management, focusing
Message-ID: <4977@helios.ee.lbl.gov>
Date: 28 Feb 90 21:21:50 GMT
References: <2928@trwind.UUCP>
Sender: usenet@helios.ee.lbl.gov
Reply-To: envbvs@epb2.lbl.gov (Brian V. Smith)
Organization: lbl
Lines: 19
X-Local-Date: 28 Feb 90 13:21:50 PST

In article <2928@trwind.UUCP>, simpson@saturn.ind.trw.com (Scott
Simpson) writes:
> I recently switch from uwm to twm and an old problem I noticed in twm
> still exists.  When my machine gets somewhat loaded and I move the cursor
> to a new window and start typing, twm doesn't always catch up and the input
> goes to the other window.  This never happened with uwm and is the main
> reason I used to use it.  Is there any way to tell twm to check the times
> of pointer and keyboard events so it knows which window keyboard input
> is supposed to go to, regardless of whether it has caught up yet?
> Scott Simpson    TRW Information Networks Division    simpson@trwind.trw.com

You have to set "NoTitleFocus" in your .twmrc file.
There is apparently a race condition if you allow keyboard focus in the 
title bar.  This will prevent the problem you are having.

_____________________________________
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
I don't speak for LBL, these non-opinions are all mine.