From: Pierre Ossman <ossman@cendio.se>
Date: Fri, 22 Sep 2017 14:48:14 +0000 (+0200)
Subject: Make sure to start the frame timer after a buffer change
X-Git-Tag: v1.8.90~99
X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=b1e80f7b025db4086e60f0867dce425838c171f3;p=tigervnc.git

Make sure to start the frame timer after a buffer change

The buffer is considered changed right away, so we might not get any
add_changed() calls to trigger a start of the timer.
---

diff --git a/common/rfb/VNCServerST.cxx b/common/rfb/VNCServerST.cxx
index 43e8f3ed..46c4be9b 100644
--- a/common/rfb/VNCServerST.cxx
+++ b/common/rfb/VNCServerST.cxx
@@ -320,6 +320,7 @@ void VNCServerST::setPixelBuffer(PixelBuffer* pb_, const ScreenSet& layout)
 
   comparer = new ComparingUpdateTracker(pb);
   renderedCursorInvalid = true;
+  startFrameClock();
 
   // Make sure that we have at least one screen
   if (screenLayout.num_screens() == 0)