---
Hello,

        I wasn't sure whether to send this or not, but since it took me a trip 
to the protocol spec to understand, I think it's worth adding some
        information.
        Please apply as you see fit.
   
        common/rfb/VNCSConnectionST.cxx |    4 ++++
 1 file changed, 4 insertions(+)

diff --git a/common/rfb/VNCSConnectionST.cxx b/common/rfb/VNCSConnectionST.cxx
index ec2e35e..02e01b4 100644
--- a/common/rfb/VNCSConnectionST.cxx
+++ b/common/rfb/VNCSConnectionST.cxx
@@ -1089,6 +1089,10 @@ void VNCSConnectionST::writeFramebufferUpdate()
       if (i->width() && i->height()) {
         int nUpdateRects = writer()->getNumRects(*i);
         if (nUpdateRects == 0 && cp.currentEncoding() == encodingTight) {
+          // With Tight encoding and LastRect support, the client does not care
+          // about the number of rectangles in the update - it will stop 
parsing when
+          // it encounters a LastRect "rectangle".
+          // In this case, pretend to send 65535 rectangles.
           nRects = 0xFFFF;  break;
         }
         else
-- 
1.7.9.2

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Reply via email to