On Tue, 19 May 2009 15:50:47 +0200
Peter Rosin p...@lysator.liu.se wrote:
Maybe add something about the fact that it is not safe to send
SetPixelFormat messages when you have outstanding
FramebufferUpdateRequests? (which is important in the above
context...)
That was the scenario I was
Hi Pierre,
Den 2009-05-28 13:34 skrev Pierre Ossman:
The implementation of the DesktopSize (also called NewFBSize)
pseudo-encoding differs a bit between VNC families. This tries to
document a behaviour that works in the majority of the implementations.
Signed-off-by: Pierre Ossman
On Thu, 28 May 2009 14:09:45 +0200
Peter Rosin p...@lysator.liu.se wrote:
Hi Pierre,
Den 2009-05-28 13:34 skrev Pierre Ossman:
The implementation of the DesktopSize (also called NewFBSize)
pseudo-encoding differs a bit between VNC families. This tries to
document a behaviour that works
Also add some introductory text to each chapter involving gii.
Signed-off-by: Peter Rosin p...@lysator.liu.se
diff --git a/rfbproto.rst b/rfbproto.rst
index 18cda39..dfea980 100644
--- a/rfbproto.rst
+++ b/rfbproto.rst
@@ -81,7 +81,7 @@ example, a pen-based handwriting recognition engine might
On Thu, 28 May 2009 15:05:11 +0200
Peter Rosin p...@lysator.liu.se wrote:
Also add some introductory text to each chapter involving gii.
Signed-off-by: Peter Rosin p...@lysator.liu.se
Looks ok to me. Applied.
--
Pierre OssmanOpenSource-based Thin Client Technology
System
Pierre,
I'd be happy with that. Tristan allocated the numbers as XVP, so
do people think we should keep this as an abbreviation, i.e. refer
to it as XVP (virtual machine control) ..., or banish the letters
XVP completely? Personally, I'd vote to keep the XVP, just for
consistency with RealVNC's
