|
From: Federico M. Q. <fed...@no...> - 2008-12-20 04:29:36
|
On Thu, 2008-12-18 at 20:20 +0100, Peter Rosin wrote: > I believe the idea is that the server can start sending the > update before it knows exactly how many rects it will need for > the update. It can thus state that the update will contain at > least some number of rects (probably 65535) and then end the > update at will later. So, there is no need to consume the > trailing rects, the server is not supposed to add any rects > after the "last rect". I imagine that in this specific case > e.g. a ptr movement rect can be inserted in the middle of a > number of tight rects, even if the ptr movement happened after > the update "started". Yes, exactly. This is GVNC_ENCODING_CURSOR_POS, which is currently not handled. If we advertise it as supported, Xvnc can send pointer updates in the middle of the string of rectangles. Federico |