Browse Source

[Development] Disabling special video encoding when the VideoPriority parameter is 0. In this case, video updates will be encoded similarly to normal updates.


git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@3402 3789f03b-4d11-0410-bbf8-ca57d06f2519
tags/v0.0.90
Constantin Kaplinsky 15 years ago
parent
commit
a09dc14bae
2 changed files with 10 additions and 2 deletions
  1. 1
    2
      common/rfb/ServerCore.cxx
  2. 9
    0
      common/rfb/VNCSConnectionST.cxx

+ 1
- 2
common/rfb/ServerCore.cxx View File

@@ -94,8 +94,7 @@ rfb::BoolParameter rfb::Server::queryConnect
false);

// TightVNC-specific parameters
// FIXME: Disable special video handling when this parameter is 0.
rfb::IntParameter rfb::Server::videoPriority
("VideoPriority",
"Priority of sending updates for video area (0..8)",
"Priority of sending video updates (0..8)",
2, 0, 8);

+ 9
- 0
common/rfb/VNCSConnectionST.cxx View File

@@ -565,6 +565,15 @@ void VNCSConnectionST::writeFramebufferUpdate()
server->checkUpdate();
}

// If VideoPriority is 0, convert video updates to normal updates.

if (rfb::Server::videoPriority == 0) {
// Region videoRegion(updates.getVideoArea());
// updates.add_changed(videoRegion);
Rect nullRect(0, 0, 0, 0);
updates.set_video_area(nullRect);
}

// Get the lists of updates. Prior to exporting the data to the `ui' object,
// getUpdateInfo() will normalize the `updates' object such way that its
// `changed', `copied' and `video_area' regions would not intersect.

Loading…
Cancel
Save