aboutsummaryrefslogtreecommitdiff
path: root/nxcomp/GetImageReply.cpp
diff options
context:
space:
mode:
authorMihai Moldovan <ïonic@ionic.de>2016-06-28 23:54:17 +0000
committerMihai Moldovan <ïonic@ionic.de>2016-07-28 03:26:00 +0000
commitbb9b50bfcf9c656367b7a9b6b5c73fea6c21a718 (patch)
treed41174f6f42d8ffb5e37246b5106e33f1588275d /nxcomp/GetImageReply.cpp
parent6effea543d04150ca0d5aa6d4b5edadfd320ea17 (diff)
downloadnx-libs-bb9b50bfcf9c656367b7a9b6b5c73fea6c21a718.tar.gz
nx-libs-bb9b50bfcf9c656367b7a9b6b5c73fea6c21a718.tar.bz2
nx-libs-bb9b50bfcf9c656367b7a9b6b5c73fea6c21a718.zip
nx-X11/programs/Xserver/hw/nxagent/Display.c: use new ReconnectTolerance nxagentOption value in nxagentCheckForDepthsCompatibility() and modify behavior based on this value.
Recognized values: - Strict means that the number of old and new depths must match exactly and every old depth value must be available in the new depth array. - Safe means that the number of depths might diverge, but all former depth must also be included in the new depth array. This is recommended, because it allows clients with more depths to still connect, but not lose functionality. - Risky means that the new depths array is allowed to be smaller than the old depths array, but at least one depth value must be included in both. This is potentially unsafe. - Bypass or higher means that all of these checks are essentially deactivated. This is a very bad idea. Note that the default ReconnectTolerance value is still Strict.
Diffstat (limited to 'nxcomp/GetImageReply.cpp')
0 files changed, 0 insertions, 0 deletions