That's very interesting. I've had reports that VNC can repeatedly end up
sending the pointer under certain circumstances and this may well provide an
explanation as to why, if the Windows client is erroneously sending
duplicate updates.
Is there any pattern to when this occurs?
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
----- Original Message -----
From: "Paul Swift" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, March 20, 2001 11:33 AM
Subject: Many WM_MOUSEMOVE events with VNCViewer 3.3.3r7 source
> Hi,
>
> As this is my first posting to the list, I'd like to start by
congratulating
> everyone involved with VNC - it's an excellent piece of work.
>
> I recently downloaded VNC and the Windows source code (version 3.3.3r7).
>
> I have noticed that there are often 'bursts' of WM_MOUSEMOVE messages
> (trapped in ClientConnection::WndProc) where the mouse X/Y position has
not
> changed from the previous
> value.
>
> Whilst I have added code to prevent superfluous calls to
> ClientConnection::SendPointerEvent, I feel that this is still impacting on
> the performance of the viewer.
>
> I am running the viewer on Windows 2000 (SP1).
>
> Has anyone else observed this behaviour?
>
> Regards,
> Paul Swift
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
