Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!dog.ee.lbl.gov!epb2.lbl.gov!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.windows.x
Subject: Re: X server implementation problems.
Message-ID: <1990Sep6.110127@epb2.lbl.gov>
Date: 6 Sep 90 18:01:27 GMT
References: <2078@charon.cwi.nl>
Sender: usenet@dog.ee.lbl.gov
Reply-To: envbvs@epb2.lbl.gov (Brian V. Smith)
Organization: lbl
Lines: 33
X-Local-Date: Thu, 6 Sep 90 11:06:28 PDT

In article <2078@charon.cwi.nl>, jack@cwi.nl (Jack Jansen) writes:
|> I've implemented X on amoeba, our own distributed OS, and it works
|> wonderfully, but there are still two tiny problems that I can't
|> seem to track down. If anyone could point me in the right direction
|> I would be very grateful. 
|> 
   [part 1 deleted]

|> 2. The vax qvss server has a problem with twm function keys. 
|>    (entries like "F1" = : window : f.raise).
|>    Whenever you use such a function key the keyboard is assigned to
|>    the window you pressed the key over, and the only way to get it back
|>    again is iconifying or destroying the window. I have been looking at
|>    the KeyGrab stuff, but I'm rather lost there. Moreover, it seems
|>    to be a machine dependent problem, because the sun server has no
|>    problems.
|> 

I don't know why  you are having this second problem - we have been
using Xqvss on our vaxstation II's and 2000's for a few years now, and
we never have a problem with the window grabbing the keyboard as you
describe.  
Here are some examples of our function key bindings from .twmrc:

"F1"    =       : window        : f.lower
"F6"    =       : window        : f.iconify
"F7"    =       : window        : f.fullzoom
"F10"   =       : window        : f.raiselower

--
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
I don't speak for LBL; they don't pay me enough for that.