What issues with the local cursors are you reffering to? I have noticed
an unusual amount of server processor usage when the cursor changes.
Even on the server, the cursor takes about 0.5 seconds to change shape.
I don't know if it is because of the processor being bogged down or
something tight vnc is doing to the cursor.
Even with this small problem, Tight VNC is so much better than regular
VNC and TridiaVNC combined.
Const Kaplinsky wrote:
Just to let you know. I worked on TightVNC actively during last two
weeks (mostly on Win32 local cursor issues)
---------------------------------------------------------------------
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
---------------------------------------------------------------------
