O/S hooks question

[Tim Senecal]

<snip>
>  This
>would also effectively lay the way for sending the mouse cursor only once
>when it changes, and then using a special 16x16 buffer, that's blitted onto
>the screen (we'll need special raster operations on the blits too).
>This would be more efficient than just bitblitting from what is on the
>actual screen, and a heck of a lot faster (the ability for a viewer to
>simply blit from one local buffer to another is MUCH faster than having to
>draw from data over the network).

I think this would be fantastic, if the cursor info could be seperated from
the screen data.  Since most OSs treat the cursor as a special seperate
thing anyway, this would decrease the amount of data sent by a large
amount, since all mouse movement would be removed from the remote frame
buffer.  the server could send the traditional data, mask, and "hotspot"
info whenever a cursor change occurs, as well as x and y coordinates
whenever a server side change of coordinates occurs...   the spec could
allow the client to notify the server as to what "depth" the data and mask
need to be in...

what do wez and charlie and the rest of the Xvnc gang have to say about
this?


---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------