[vwnc] 5i.4c OE won't take keyboard focus on X?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[vwnc] 5i.4c OE won't take keyboard focus on X?

Martin McClure
The scenario:

VW 5i.4c OE running on Sparc/Solaris (either Envy or normal image)
X server (X.Org 7.2) running on Linux.

VW starts OK, displays, responds normally to mouse clicks.

The problem:

None of the VW windows will take keyboard focus. All keystrokes go to
the last non-VW window to have focus.


Has anyone else seen this? Any hints on how to get around it?


I haven't had to run 5i this way for at least several months, and it
worked fine the last time I tried. The most likely change is an update
to the X server.


Thanks,

-Martin
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] 5i.4c OE won't take keyboard focus on X?

Reinout Heeck
> The scenario:
>
> VW 5i.4c OE running on Sparc/Solaris (either Envy or normal image)
> X server (X.Org 7.2) running on Linux.
>
> VW starts OK, displays, responds normally to mouse clicks.
>
> The problem:
>
> None of the VW windows will take keyboard focus. All keystrokes go to
> the last non-VW window to have focus.
>
>
> Has anyone else seen this? Any hints on how to get around it?
>
>
> I haven't had to run 5i this way for at least several months, and it
> worked fine the last time I tried. The most likely change is an update
> to the X server.




The following is from a dim memory of many many years ago, please take  
it with a large grain of salt:

In those days I could only get VW to work on a split X environment if  
both server and client libraries were of the same foundry.
I recall having a look at the VM sources and noticing that that VM  
caches several properties of the X client and then pretends these  
properties apply equally to the X server. I also vaguely recall that  
the VM would ask for the vendor tag of the X client and then applying  
settings from a hard-coded vendor->properties map in the VM -- this  
whole setup wouldn't ask what the vendor of the XServer is, it just  
assumed it would be the same as the client.

Needless to say this falls apart in certain scenarios. My symptoms  
were more severe though, the whole X connection would hang somewhere  
during connection build-up. No VW windows visible...

I don't know whether this still applies in the case of 5.4c and my  
memory is vague anyway -- but here you have it ;-)



R
-


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc