VirtualGL

Email Archive: virtualgl-users (read-only)

2007:	_Jan (1)	_Feb (5)	_Mar (7)	_Apr (7)	_May (1)	_Jun (10)	_Jul (5)	_Aug (4)	_Sep (16)	_Oct (2)	_Nov (8)	_Dec (3)
2008:	_Jan (6)	_Feb (18)	_Mar (6)	_Apr (5)	_May (15)	_Jun (6)	_Jul (23)	_Aug (5)	_Sep (9)	_Oct (15)	_Nov (7)	_Dec (3)
2009:	_Jan (22)	_Feb (13)	_Mar (15)	_Apr (3)	_May (19)	_Jun (1)	_Jul (44)	_Aug (16)	_Sep (13)	_Oct (32)	_Nov (34)	_Dec (6)
2010:	_Jan (5)	_Feb (27)	_Mar (28)	_Apr (29)	_May (19)	_Jun (30)	_Jul (14)	_Aug (5)	_Sep (17)	_Oct (10)	_Nov (13)	_Dec (13)
2011:	_Jan (18)	_Feb (34)	_Mar (57)	_Apr (39)	_May (28)	_Jun (2)	_Jul (7)	_Aug (17)	_Sep (28)	_Oct (25)	_Nov (17)	_Dec (15)
2012:	_Jan (15)	_Feb (47)	_Mar (40)	_Apr (15)	_May (15)	_Jun (34)	_Jul (44)	_Aug (66)	_Sep (34)	_Oct (8)	_Nov (37)	_Dec (23)
2013:	_Jan (14)	_Feb (26)	_Mar (38)	_Apr (27)	_May (30)	_Jun	_Jul	_Aug	_Sep	_Oct	_Nov	_Dec


S	M	T	W	T	F	S
1	2	3	4	5	6	7
			(1)
8	9	10	11	12	13	14

15	16	17	18	19	20	21

22	23	24	25	26	27	28

29	30
	(6)

[VirtualGL-Users] Error: Xlib: extension "GLX" missing on display ":1.0".

From: Adam Thomas <virtualgl@ad...> - 2007-04-30 13:01

Attachments: Message as HTML

Hello,

I'm trying to install TurboVNC on a Redhat 9 box with an  NVIDIA GPU Quadro4
750 XG card and NVIDIA driver version 1.0.9631. I'm working with the
2.0-el3rpm of VirtualGL,
1.10.2 for turbojpeg, and 0.3.2 for turbovnc. The TurboVNC client (also
0.3.2) is running on Windows XP.

OpenGL application work fine on the console and through NX (
http://www.nomachine.com/). However when I try to launch an OpenGL
application inside a turboVNC window, I get the following error:

Xlib:  extension "GLX" missing on display ":1.0".
trying lame single buffer visual
Warning: trying lame single buffer visual
Xlib:  extension "GLX" missing on display ":1.0".
Error: no good visual

Can anyone advise me on what's going wrong?

Thanks,
-Adam Thomas

Re: [VirtualGL-Users] Error: Xlib: extension "GLX" missing on display":1.0".

From: DRC <dcommander@us...> - 2007-04-30 13:34

Attachments: Message as HTML

Are you invoking the OpenGL application with
 
vglrun {application}
 
??
 
TurboVNC (or any VNC, for that matter) does not support GLX, thus you have
to use VirtualGL to redirect the GLX commands from the application to the
"real" X server, which is attached to the 3D hardware.  VirtualGL then reads
back the rendered 3D frames from the 3D hardware and draws the frames as 2D
X Images in TurboVNC.
 
NoMachine NX does support the GLX extension, which is why your application
works in that environment without invoking vglrun.  However, NX's
implementation of GLX is not hardware-accelerated, so you would still need
to use VirtualGL and invoke the application with vglrun in order to get 3D
hardware acceleration in NX.
 
The upcoming VirtualGL 2.0.1 release has more clear documentation on how to
use TurboVNC with VirtualGL.  You can get a sneak preview of this here:
http://www.virtualgl.org/vgldoc/2_0/#hd0010
 
The instructions in this new documentation should be applicable to VGL 2.0
as well.

[-=DRC=-]


 


  _____  

From: virtualgl-users-bounces@...
[mailto:virtualgl-users-bounces@...] On Behalf Of Adam
Thomas
Sent: Monday, April 30, 2007 8:01 AM
To: virtualgl-users@...
Subject: [VirtualGL-Users] Error: Xlib: extension "GLX" missing on
display":1.0".


Hello,

I'm trying to install TurboVNC on a Redhat 9 box with an  NVIDIA GPU Quadro4
750 XG card and NVIDIA driver version 1.0.9631. I'm working with the 2.0-el3
rpm of VirtualGL, 1.10.2 for turbojpeg, and 0.3.2 for turbovnc. The TurboVNC
client (also 0.3.2) is running on Windows XP.

OpenGL application work fine on the console and through NX
(http://www.nomachine.com/). However when I try to launch an OpenGL
application inside a turboVNC window, I get the following error: 

Xlib:  extension "GLX" missing on display ":1.0".
trying lame single buffer visual
Warning: trying lame single buffer visual
Xlib:  extension "GLX" missing on display ": 1.0".
Error: no good visual

Can anyone advise me on what's going wrong?

Thanks,
-Adam Thomas

Re: [VirtualGL-Users] Error: Xlib: extension "GLX" missing on display":1.0".

From: Adam Thomas <virtualgl@ad...> - 2007-04-30 15:07

Attachments: Message as HTML

Thanks, I had missed that in the docs. I tried it with vglrun, but I'm now
getting a permissions error:

[vnc@... vnc]$ vglrun suma

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

[VGL] Could not open display :0.
[vnc@... vnc]$ echo $DISPLAY
:1.0
[vnc@... vnc]$ vglrun -d $DISPLAY suma

Xlib:  extension "GLX" missing on display ":1.0".
trying lame single buffer visual
Warning: trying lame single buffer visual
Xlib:  extension "GLX" missing on display ":1.0".
Error: no good visual


Can you advise?

Thanks,
-Adam


On 4/30/07, DRC <dcommander@...> wrote:
>
>  Are you invoking the OpenGL application with
>
> vglrun {application}
>
> ??
>
> TurboVNC (or any VNC, for that matter) does not support GLX, thus you have
> to use VirtualGL to redirect the GLX commands from the application to the
> "real" X server, which is attached to the 3D hardware.  VirtualGL then reads
> back the rendered 3D frames from the 3D hardware and draws the frames as 2D
> X Images in TurboVNC.
>
> NoMachine NX does support the GLX extension, which is why your application
> works in that environment without invoking vglrun.  However, NX's
> implementation of GLX is not hardware-accelerated, so you would still need
> to use VirtualGL and invoke the application with vglrun in order to get 3D
> hardware acceleration in NX.
>
> The upcoming VirtualGL 2.0.1 release has more clear documentation on how
> to use TurboVNC with VirtualGL.  You can get a sneak preview of this here:
> http://www.virtualgl.org/vgldoc/2_0/#hd0010
>
> The instructions in this new documentation should be applicable to VGL 2.0as well.
>
> [-=DRC=-]
>
>
>  ------------------------------
> *From:* virtualgl-users-bounces@... [mailto:
> virtualgl-users-bounces@...] *On Behalf Of *Adam Thomas
> *Sent:* Monday, April 30, 2007 8:01 AM
> *To:* virtualgl-users@...
> *Subject:* [VirtualGL-Users] Error: Xlib: extension "GLX" missing on
> display":1.0".
>
> Hello,
>
> I'm trying to install TurboVNC on a Redhat 9 box with an  NVIDIA GPU
> Quadro4 750 XG card and NVIDIA driver version 1.0.9631. I'm working with
> the 2.0-el3 rpm of VirtualGL, 1.10.2 for turbojpeg, and 0.3.2 for
> turbovnc. The TurboVNC client (also 0.3.2) is running on Windows XP.
>
> OpenGL application work fine on the console and through NX (
> http://www.nomachine.com/). However when I try to launch an OpenGL
> application inside a turboVNC window, I get the following error:
>
> Xlib:  extension "GLX" missing on display ":1.0".
> trying lame single buffer visual
> Warning: trying lame single buffer visual
> Xlib:  extension "GLX" missing on display ": 1.0".
> Error: no good visual
>
> Can anyone advise me on what's going wrong?
>
> Thanks,
> -Adam Thomas
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> VirtualGL-Users mailing list
> VirtualGL-Users@...
> https://lists.sourceforge.net/lists/listinfo/virtualgl-users
>
>

Re: [VirtualGL-Users] Error: Xlib: extension "GLX" missing ondisplay":1.0".

From: DRC <dcommander@us...> - 2007-04-30 15:51

Attachments: Message as HTML

The documentation explains how to open up permissions on display :0 (using
xauth) so that VGL can access it.  VirtualGL has to be able to access
display :0 because that's the display that is connected to the 3D hardware.
It doesn't actually display anything on display :0, but it has to go through
that X server so it can create OpenGL Pbuffers in which to do the 3D
rendering.
 
VirtualGL's approach is called "split rendering", since the GLX rendering
occurs on a different X display from the rest of the X11 rendering.  The
non-3D X11 rendering is performed by VNC (display :1, in your case.)

[-=DRC=-]


 


  _____  

From: virtualgl-users-bounces@...
[mailto:virtualgl-users-bounces@...] On Behalf Of Adam
Thomas
Sent: Monday, April 30, 2007 10:08 AM
To: VirtualGL Users
Subject: Re: [VirtualGL-Users] Error: Xlib: extension "GLX" missing
ondisplay":1.0".



Thanks, I had missed that in the docs. I tried it with vglrun, but I'm now
getting a permissions error:

[vnc@... vnc]$ vglrun suma

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified 

[VGL] Could not open display :0.
[vnc@... vnc]$ echo $DISPLAY
:1.0
[vnc@... vnc]$ vglrun -d $DISPLAY suma

Xlib:  extension "GLX" missing on display ":1.0".
trying lame single buffer visual 
Warning: trying lame single buffer visual
Xlib:  extension "GLX" missing on display ":1.0".
Error: no good visual


Can you advise?

Thanks,
-Adam



On 4/30/07, DRC <dcommander@...> wrote: 

Are you invoking the OpenGL application with
 
vglrun {application}
 
??
 
TurboVNC (or any VNC, for that matter) does not support GLX, thus you have
to use VirtualGL to redirect the GLX commands from the application to the
"real" X server, which is attached to the 3D hardware.  VirtualGL then reads
back the rendered 3D frames from the 3D hardware and draws the frames as 2D
X Images in TurboVNC.
 
NoMachine NX does support the GLX extension, which is why your application
works in that environment without invoking vglrun.  However, NX's
implementation of GLX is not hardware-accelerated, so you would still need
to use VirtualGL and invoke the application with vglrun in order to get 3D
hardware acceleration in NX.
 
The upcoming VirtualGL 2.0.1 release has more clear documentation on how to
use TurboVNC with VirtualGL.  You can get a sneak preview of this here:
http://www.virtualgl.org/vgldoc/2_0/#hd0010
<http://www.virtualgl.org/vgldoc/2_0/#hd0010> 
 
The instructions in this new documentation should be applicable to VGL 2.0
as well.

[-=DRC=-]


 


  _____  

From: virtualgl-users-bounces@...
[mailto:virtualgl-users-bounces@...] On Behalf Of Adam
Thomas
Sent: Monday, April 30, 2007 8:01 AM
To: virtualgl-users@...
Subject: [VirtualGL-Users] Error: Xlib: extension "GLX" missing on
display":1.0".



Hello,

I'm trying to install TurboVNC on a Redhat 9 box with an  NVIDIA GPU Quadro4
750 XG card and NVIDIA driver version 1.0.9631. I'm working with the 2.0-el3
rpm of VirtualGL, 1.10.2 for turbojpeg, and 0.3.2 for turbovnc. The TurboVNC
client (also 0.3.2) is running on Windows XP.

OpenGL application work fine on the console and through NX
(http://www.nomachine.com/). However when I try to launch an OpenGL
application inside a turboVNC window, I get the following error: 

Xlib:  extension "GLX" missing on display ":1.0".
trying lame single buffer visual
Warning: trying lame single buffer visual
Xlib:  extension "GLX" missing on display ": 1.0".
Error: no good visual

Can anyone advise me on what's going wrong?

Thanks,
-Adam Thomas




-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now. 
http://sourceforge.net/powerbar/db2/
_______________________________________________
VirtualGL-Users mailing list 
VirtualGL-Users@...
https://lists.sourceforge.net/lists/listinfo/virtualgl-users

Re: [VirtualGL-Users] Error: Xlib: extension "GLX" missing ondisplay":1.0".

From: Adam Thomas <virtualgl@ad...> - 2007-04-30 19:14

Attachments: Message as HTML

I had follow the instructions in section 4.1 "Granting VirtualGL Access to
the Server's X Display," but apparently I did something wrong as I was still
getting the permission error.

I tried replacing "vglgenkey"  in /etc/X11/gdm/Init/Default with "xhost
+localhost" and now the application is working. This is sufficient for our
purposes as this is a single user machine.

Thank you for the useful program and for your assistance.

-Adam

On 4/30/07, DRC <dcommander@...> wrote:
>
>  The documentation explains how to open up permissions on display :0
> (using xauth) so that VGL can access it.  VirtualGL has to be able to access
> display :0 because that's the display that is connected to the 3D hardware.
> It doesn't actually display anything on display :0, but it has to go through
> that X server so it can create OpenGL Pbuffers in which to do the 3D
> rendering.
>
> VirtualGL's approach is called "split rendering", since the GLX rendering
> occurs on a different X display from the rest of the X11 rendering.  The
> non-3D X11 rendering is performed by VNC (display :1, in your case.)
>
> [-=DRC=-]
>
>
>  ------------------------------
> *From:* virtualgl-users-bounces@... [mailto:
> virtualgl-users-bounces@...] *On Behalf Of *Adam Thomas
> *Sent:* Monday, April 30, 2007 10:08 AM
> *To:* VirtualGL Users
> *Subject:* Re: [VirtualGL-Users] Error: Xlib: extension "GLX" missing
> ondisplay":1.0".
>
>
> Thanks, I had missed that in the docs. I tried it with vglrun, but I'm now
> getting a permissions error:
>
> [vnc@... vnc]$ vglrun suma
>
> Xlib: connection to ":0.0" refused by server
> Xlib: No protocol specified
>
> [VGL] Could not open display :0.
> [vnc@... vnc]$ echo $DISPLAY
> :1.0
> [vnc@... vnc]$ vglrun -d $DISPLAY suma
>
> Xlib:  extension "GLX" missing on display ":1.0".
> trying lame single buffer visual
> Warning: trying lame single buffer visual
> Xlib:  extension "GLX" missing on display ":1.0".
> Error: no good visual
>
>
> Can you advise?
>
> Thanks,
> -Adam
>
>
> On 4/30/07, DRC <dcommander@...> wrote:
> >
> >  Are you invoking the OpenGL application with
> >
> > vglrun {application}
> >
> > ??
> >
> > TurboVNC (or any VNC, for that matter) does not support GLX, thus you
> > have to use VirtualGL to redirect the GLX commands from the application to
> > the "real" X server, which is attached to the 3D hardware.  VirtualGL then
> > reads back the rendered 3D frames from the 3D hardware and draws the
> > frames as 2D X Images in TurboVNC.
> >
> > NoMachine NX does support the GLX extension, which is why your
> > application works in that environment without invoking vglrun.  However,
> > NX's implementation of GLX is not hardware-accelerated, so you would still
> > need to use VirtualGL and invoke the application with vglrun in order to get
> > 3D hardware acceleration in NX.
> >
> > The upcoming VirtualGL 2.0.1 release has more clear documentation on how
> > to use TurboVNC with VirtualGL.  You can get a sneak preview of this here:
> > http://www.virtualgl.org/vgldoc/2_0/#hd0010
> >
> > The instructions in this new documentation should be applicable to VGL
> > 2.0 as well.
> >
> > [-=DRC=-]
> >
> >
> >  ------------------------------
> > *From:* virtualgl-users-bounces@... [mailto:
> > virtualgl-users-bounces@...] *On Behalf Of *Adam
> > Thomas
> > *Sent:* Monday, April 30, 2007 8:01 AM
> > *To:* virtualgl-users@...
> > *Subject:* [VirtualGL-Users] Error: Xlib: extension "GLX" missing on
> > display":1.0".
> >
> >  Hello,
> >
> > I'm trying to install TurboVNC on a Redhat 9 box with an  NVIDIA GPU
> > Quadro4 750 XG card and NVIDIA driver version 1.0.9631. I'm working with
> > the 2.0-el3 rpm of VirtualGL, 1.10.2 for turbojpeg, and 0.3.2 for
> > turbovnc. The TurboVNC client (also 0.3.2) is running on Windows XP.
> >
> > OpenGL application work fine on the console and through NX (
> > http://www.nomachine.com/). However when I try to launch an OpenGL
> > application inside a turboVNC window, I get the following error:
> >
> > Xlib:  extension "GLX" missing on display ":1.0".
> > trying lame single buffer visual
> > Warning: trying lame single buffer visual
> > Xlib:  extension "GLX" missing on display ": 1.0".
> > Error: no good visual
> >
> > Can anyone advise me on what's going wrong?
> >
> > Thanks,
> > -Adam Thomas
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > VirtualGL-Users mailing list
> > VirtualGL-Users@...
> > https://lists.sourceforge.net/lists/listinfo/virtualgl-users
> >
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> VirtualGL-Users mailing list
> VirtualGL-Users@...
> https://lists.sourceforge.net/lists/listinfo/virtualgl-users
>
>

Re: [VirtualGL-Users] Error: Xlib: extension "GLX" missingondisplay":1.0".

From: DRC <dcommander@us...> - 2007-04-30 19:45

Attachments: Message as HTML

Not sure why vglgenkey wasn't working.  Possibly the permissions on
/etc/opt/VirtualGL didn't allow your account to read the key that vglgenkey
stores in that directory.  But yeah, on a single user machine 'xhost
+localhost' works just as well.

[-=DRC=-]


 


  _____  

From: virtualgl-users-bounces@...
[mailto:virtualgl-users-bounces@...] On Behalf Of Adam
Thomas
Sent: Monday, April 30, 2007 2:09 PM
To: VirtualGL Users
Subject: Re: [VirtualGL-Users] Error: Xlib: extension "GLX"
missingondisplay":1.0".


I had follow the instructions in section 4.1 "Granting VirtualGL Access to
the Server's X Display," but apparently I did something wrong as I was still
getting the permission error.

I tried replacing "vglgenkey"  in /etc/X11/gdm/Init/Default with "xhost
+localhost" and now the application is working. This is sufficient for our
purposes as this is a single user machine. 

Thank you for the useful program and for your assistance.

-Adam


On 4/30/07, DRC <dcommander@...
<mailto:dcommander@...> > wrote: 

The documentation explains how to open up permissions on display :0 (using
xauth) so that VGL can access it.  VirtualGL has to be able to access
display :0 because that's the display that is connected to the 3D hardware.
It doesn't actually display anything on display :0, but it has to go through
that X server so it can create OpenGL Pbuffers in which to do the 3D
rendering.
 
VirtualGL's approach is called "split rendering", since the GLX rendering
occurs on a different X display from the rest of the X11 rendering.  The
non-3D X11 rendering is performed by VNC (display :1, in your case.)

[-=DRC=-]


 


  _____  

From: virtualgl-users-bounces@...
[mailto:virtualgl-users-bounces@...] On Behalf Of Adam
Thomas
Sent: Monday, April 30, 2007 10:08 AM
To: VirtualGL Users
Subject: Re: [VirtualGL-Users] Error: Xlib: extension "GLX" missing
ondisplay":1.0".




Thanks, I had missed that in the docs. I tried it with vglrun, but I'm now
getting a permissions error:

[vnc@... vnc]$ vglrun suma

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified 

[VGL] Could not open display :0.
[vnc@... vnc]$ echo $DISPLAY
:1.0
[vnc@... vnc]$ vglrun -d $DISPLAY suma

Xlib:  extension "GLX" missing on display ":1.0".
trying lame single buffer visual 
Warning: trying lame single buffer visual
Xlib:  extension "GLX" missing on display ":1.0".
Error: no good visual


Can you advise?

Thanks,
-Adam



On 4/30/07, DRC <dcommander@...> wrote: 

Are you invoking the OpenGL application with
 
vglrun {application}
 
??
 
TurboVNC (or any VNC, for that matter) does not support GLX, thus you have
to use VirtualGL to redirect the GLX commands from the application to the
"real" X server, which is attached to the 3D hardware.  VirtualGL then reads
back the rendered 3D frames from the 3D hardware and draws the frames as 2D
X Images in TurboVNC.
 
NoMachine NX does support the GLX extension, which is why your application
works in that environment without invoking vglrun.  However, NX's
implementation of GLX is not hardware-accelerated, so you would still need
to use VirtualGL and invoke the application with vglrun in order to get 3D
hardware acceleration in NX.
 
The upcoming VirtualGL 2.0.1 release has more clear documentation on how to
use TurboVNC with VirtualGL.  You can get a sneak preview of this here:
http://www.virtualgl.org/vgldoc/2_0/#hd0010
<http://www.virtualgl.org/vgldoc/2_0/#hd0010> 
 
The instructions in this new documentation should be applicable to VGL 2.0
as well.

[-=DRC=-]


 


  _____  

From: virtualgl-users-bounces@...
<mailto:virtualgl-users-bounces@...>
[mailto:virtualgl-users-bounces@...] On Behalf Of Adam
Thomas
Sent: Monday, April 30, 2007 8:01 AM
To: virtualgl-users@...
Subject: [VirtualGL-Users] Error: Xlib: extension "GLX" missing on
display":1.0".



Hello,

I'm trying to install TurboVNC on a Redhat 9 box with an  NVIDIA GPU Quadro4
750 XG card and NVIDIA driver version 1.0.9631. I'm working with the 2.0-el3
rpm of VirtualGL, 1.10.2 for turbojpeg, and 0.3.2 for turbovnc. The TurboVNC
client (also 0.3.2) is running on Windows XP.

OpenGL application work fine on the console and through NX
(http://www.nomachine.com/). However when I try to launch an OpenGL
application inside a turboVNC window, I get the following error: 

Xlib:  extension "GLX" missing on display ":1.0".
trying lame single buffer visual
Warning: trying lame single buffer visual
Xlib:  extension "GLX" missing on display ": 1.0".
Error: no good visual

Can anyone advise me on what's going wrong?

Thanks,
-Adam Thomas




-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now. 
http://sourceforge.net/powerbar/db2/
_______________________________________________ 
VirtualGL-Users mailing list 
VirtualGL-Users@...
https://lists.sourceforge.net/lists/listinfo/virtualgl-users





-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now. 
http://sourceforge.net/powerbar/db2/
_______________________________________________
VirtualGL-Users mailing list 
VirtualGL-Users@...
https://lists.sourceforge.net/lists/listinfo/virtualgl-users

Re: [VirtualGL-Users] Multiple key strokes

From: DRC <dcommander@us...> - 2007-04-04 20:45

Attachments: Message as HTML

Sorry for the delayed reply.  We've been busy with getting VirtualGL 2.0.1
ready for release.
 
I'm not sure if there is a straightforward way to do what you're proposing.
The issue is that TurboVNC doesn't really know when a key is being held
down.  It just passes keystrokes through blindly from the client to the
server.  So if the client's window manager is automatically generating
multiple keystroke events in response to the key being held down, TurboVNC
has no way of knowing this.  The only way to disable key repeat is to
disable it in the client's window manager.

[-=DRC=-]


 


  _____  

From: virtualgl-users-bounces@...
[mailto:virtualgl-users-bounces@...] On Behalf Of Coe,
Colin C. (Unix Engineer)
Sent: Tuesday, March 27, 2007 1:57 AM
To: VirtualGL Users
Subject: Re: [VirtualGL-Users] Multiple key strokes


Apologies all, This got lost in all the excitement...
 
The main user has responded with
 
---
Ok the application is a propietry one from Shell used for interpreting
seismic( like a massive MRI cube of data), We've tested the application with
the virtualGL and turbovnc viewer on a PC and the server on a Linux box .
The behaviours one each that are not the same are as  follows:
 
direct in the application on a desktop:      to scroll the slices around the
volume it uses hot keys to change modes to make it fast.  These as all Ok in
the application on a desktop linux machines we have.  ie if I hold down the
spacebar and push with the mouse and it will what is known as drag the slice
away from me thru the volume.    
 
On a turbovnc session on a PC: attaching to the linux : the holding down of
the spacebar is the biggest issue, it causes the mode change required to
drag the slices around to not be recognised.   
 
So we need a way of adding to the special keystrokes the can be set as a
variable when starting the session,  When I set sticky keys on the PC,
everything works Ok but that affects all applications, we need it only for
the turbovnc window to not pass multiple spacebar keys when held down.
---
 
Thanks
 
CC
 

-----Original Message-----
From: virtualgl-users-bounces@...
[mailto:virtualgl-users-bounces@...] On Behalf Of DRC
Sent: Tuesday, 20 March 2007 1:55 PM
To: 'VirtualGL Users'
Subject: Re: [VirtualGL-Users] Multiple key strokes


It sounds as if that might be an artifact of TurboVNC rather than VirtualGL.
VirtualGL doesn't do anything to modify the keystroke behavior of the
application, but since TurboVNC is a different X server, it might have
different behavior in this regard.  Can you provide more information about
the application?  Perhaps steps to reproduce the problem?

[-=DRC=-]


 



The issue still remains that multiple key strokes( eg <spbr>)  used in the
software to invoke a different mode ( eg from rotate to drag object)

On a normal desktop system we have, the space bar held down is interpreted
as multiple key strokes but using virtualGL its not functioning that way, I
can go to Sticky keys in windows but that affects all applications on the
client, I'd really like a virtualGL setting that can be invoked at startup
that sets multiply keystrokes ignore only in the virtualGL window.

NOTICE: This email and any attachments are confidential. 

They may contain legally privileged information or 

copyright material. You must not read, copy, use or 

disclose them without authorisation. If you are not an 

intended recipient, please contact us at once by return 

email and then delete both messages and all attachments.