vncviewer 4.0 on XP, problems with cursor positioning from
jnw "at" realvnc.com
Wed Dec 15 13:58:01 2004
Pseudo-encoding 0xffffff11 does not affect the cursor position, only the
cursor "shape" and hotspot. Your custom server is either sending the
pseudo-encoding to a viewer that hasn't said that it can support it via
SetEncodings (e.g. VNC Viewer 3.3.7), or is sending incorrectly-formatted
cursor data to a viewer that *does* support the cursor shape encoding (e.g.
VNC Viewer 4). Also be aware that the cursor can only be sent as part of a
framebuffer update, since its format must match the format currently
requested by the VNC Viewer, which can change between updates.
Please remember that any code based on the standard VNC codebase must be
distributed under the provisions of the GPL. :)
Wez @ RealVNC Ltd.
> -----Original Message-----
> From: vnc-list-admin "at" realvnc.com
> [mailto:vnc-list-admin "at" realvnc.com] On Behalf Of Michael Russe
> Sent: 15 December 2004 13:01
> To: vnc-list "at" realvnc.com
> Subject: vncviewer 4.0 on XP, problems with cursor
> positioning from server side
> Hi, I wrote my own rfb server for an application which does
> not use X nor
> Windows. I am testing against the latest download from
> realvnc.com. Everything
> works great until I need to set the cursor position on the
> client side from my
> server. I am doing this by sending a 5x5 rectangle with a 5
> byte mask with
> encoding set to 0xffffff11 as part of an answer to a
> framebuffer update
> request. The viewer will paint some strange patterns around the cursor
> position and crash so bad that MS wants to know about it.
> Can anybody give me a hint what might be going on and what to change ?
> Thanks, Michael
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: