[comp.windows.x] X server implementation problems.

jack@cwi.nl (Jack Jansen) (09/06/90)

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. 

1. The BW2 sun server (code based on the unix sun server as distributed)
   makes the mouse cursor disappear if a new window is opened where the
   mouse currently is. Moving the mouse will make it reappear. I assume
   this problem is somewhere in the mi stuff (since that seems to be used to
   make the cursor disappear and appear again) but I don't have a clue where to
   look.

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.

Any help is greatly appreciated. If you post to the group, please mail
to me as well, since I will be gone for a few weeks so I'll probably
miss any answers posted to the group.
--
--
Een volk dat voor tirannen zwicht	| Oral:     Jack Jansen
zal meer dan lijf en goed verliezen	| Internet: jack@cwi.nl
dan dooft het licht			| Uucp:     hp4nl!cwi.nl!jack

envbvs@epb2.lbl.gov (Brian V. Smith) (09/07/90)

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.

keith@EXPO.LCS.MIT.EDU (Keith Packard) (09/07/90)

> 1. The BW2 sun server (code based on the unix sun server as distributed)
>    makes the mouse cursor disappear if a new window is opened where the
>    mouse currently is. Moving the mouse will make it reappear. I assume
>    this problem is somewhere in the mi stuff (since that seems to be used to
>    make the cursor disappear and appear again) but I don't have a clue where to
>    look.

The cursor reappears when miSpriteBlockHandler is called from BlockHandler
which is called from WaitForSomething just before select is called to await
additional data from the network.