Brian,
The VNC X desktop is the X desktop that you are accessing via VNC. What
you want is for the keyboard-repeat settings at the viewer computer to
apply, rather than having the X server "fake" keyboard repeats, since
the latter will lead to spurious repeats if a key-release event gets
delayed for some reason.
Regards,
Wez @ RealVNC Ltd.
Brian Auld wrote:
For clarification, when you say "VNC X desktop", are you referring to
the VNC client or VNC server side? I did browse through my options on
the VNC client side and do not recall seeing anything re: keyboard
repeat.
Thanks,
Brian
-----Original Message-----
From: James Weatherall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 16, 2006 4:12 AM
To: Brian Auld; [email protected]
Subject: RE: keystroke spewage
Brian,
It sounds like your VNC X desktop has keyboard repeat enabled - you
should disable this in order to avoid "spewage".
Regards,
Wez @ RealVNC Ltd.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Auld
Sent: 16 August 2006 01:41
To: [email protected]
Subject: keystroke spewage
I am new to using VNC and am having a frustrating problem with
keystroke spewage. While connected to my remote app, I'll type a
keystroke and it will ultimately be echoed to my application multiple
times.
My setup is
as follows:
Environment
-----------
Client: VNC4.1.2 on winxp sp2
Network: Internet - VPN client (cisco 4.0.5)
Server: Fedora 3 running vnc server provided with distro
(vnc-server-4.0-8).
Remote app: emacs (emacs-21.3-17). This is what I always use, but
I've also seen spewage in xterms etc...
I googled for 'keystroke repeated vnc' etc... and various permutations
and combinations of similar english text and did not find anything
useful.
Any history on this or solution would be appreciated.
VNC aside, I've used the same setup to run other apps via vpn and have
not seen this problem. If keystrokes are sent 1 character at a time
over the network, it almost seems like the vnc client app is resending
the packet for a given keystroke because it perceives the prior packet
(keystroke) to have been dropped ... when in fact they all arrive and
barf all over my screen. This problem is intermittent, so network
latency could very well be a large contributing factor.
Regards,
Brian Auld
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list