From: Sean Kamath <kamath@ge...> - 2006-02-15 01:55:42
Did anyone notice on the RealVNC mailing list a note that on
low-bandwidth connections one should turn on "Pointer rate-limiting"?
"Over very slow lines such as those, you'll want to enable "Pointer
rate-limiting" in VNC Viewer. Without this, the channel from server to
viewer can get saturated with TCP acknowledgements, preventing updates from
I sent him a private note asking how they do it, but then saw in a
followup this note:
"The option in question is PointerEventInterval, e.g.
Will specify that pointer movement events should normally be sent only every
So, I know that in the past the recommendation has been to not have
the end-user deal with a million options, but I'm of the opinion that
options *should* be available for tweaking, just not *NECESSARY* to
tweak. I.e., I think there should be an option in each profile to
have this mouse-tweak (perhaps not giving the delay time) and have a
command line option or other (global?) preference for the amount of
Of course, if it were me, I'd have a global (do/don't + ms delay) and
each profile would "inherit" the default unless it was overridden.
[In a message on Mon, 13 Feb 2006 20:38:35 MST,
Jason Harris wrote:]
>Maybe it would be a good idea to mention it on the ArsTechnica Mac
>forums. There are a lot of tech-savvy Chicken users there.
>On Feb 13, 2006, at 5:30 PM, Jared McIntyre wrote:
>> At 9:23 AM -0700 2/13/06, Jason Harris wrote:
>>> I'm sorry, I haven't played with this. The only server I ever had
>>> mouse issues with was Tight on Windows, which I use only for
>>> testing, and find to be generally brain-dead.
>>> Don't feel bad about not working on Chicken! Real life comes
>>> waaaay before volunteer work! :)
>> It is certainly not "necessary" for most servers, but I still find
>> it an improvement. I was hoping others would take a look at it to
>> see if we wanted to put something like that in as an option, or
>> perhaps provide it in a fashion that can be throttled in different