NXv3 (redistributed) https://openid.arctica-project.org/nx-libs/atom?h=3.5.99.3 2016-11-15T15:38:26+00:00 2016-11-15T15:38:26+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2016-11-02T23:19:26+00:00 urn:sha1:80b5de3f55fd493ee85f2a78b731ff05e6363e43 Fixes ArcticaProject/nx-libs#276. 2016-10-20T08:16:35+00:00 Ulrich Sibiller uli42@gmx.de 2016-10-15T19:45:30+00:00 urn:sha1:81a7c6cf4af6bb865fc18bb0bcc79421fed233c8 Display.c: In function ‘nxagentCheckForPixmapFormatsCompatibility’: Display.c:2471:8: warning: variable ‘one_match’ set but not used [-Wunused-but-set-variable] bool one_match = false; ^ 2016-07-28T11:20:38+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2016-07-28T11:20:38+00:00 urn:sha1:e9a3734ae3ab5623c63c4fd0a97e1eeb23d98f41 2016-07-28T03:26:00+00:00 Mihai Moldovan ïonic@ionic.de 2016-07-03T23:52:43+00:00 urn:sha1:64a83d1e08fd8224a065d6e3548be6323127d4df Maybe needs special strictness handling as well. 2016-07-28T03:26:00+00:00 Mihai Moldovan ïonic@ionic.de 2016-07-03T23:52:06+00:00 urn:sha1:5ec7e48ac70fc88b1285e3615f7651dad1247c37 Maybe needs special strictness handling as well. 2016-07-28T03:26:00+00:00 Mihai Moldovan ïonic@ionic.de 2016-07-09T03:28:27+00:00 urn:sha1:e61c8c85cc11dad063da23fb2f1d031c574166f5 Don't implicitly call the checking function in the init function (and throw away the checking functions result...) Instead, explicitly use the checking function after the init function in other parts of the code and throw away the checking functions return value selectively or actually use it while reconnecting. This is totally different behavior compared to the original one. Hopefully it doesn't cause any problems (i.e., hopefully there was no good reason for never using the checking functions return value, but an oversight.) 2016-07-28T03:26:00+00:00 Mihai Moldovan ïonic@ionic.de 2016-06-29T02:13:03+00:00 urn:sha1:6618271493f86109103a2ade74912d34172ba569 Recognized values: - Strict means that the number of internal and external pixmap formats must match exactly and every internal pixmap format must be available in the external pixmap format array. - Safe means that the number of pixmap formats might diverge, but all internal pixmap formats must also be included in the external pixmap formats array. This is recommended, because it allows clients with more pixmap formats to still connect, but not lose functionality. - Risky means that the internal pixmap formats array is allowed to be smaller than the external pixmap formats array, but at least one pixmap format 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. Also, the return value of this function is currently not used or passed through to other functions at all. An upcoming commit will change this behavior and actually enable the checks. 2016-07-28T03:26:00+00:00 Mihai Moldovan ïonic@ionic.de 2016-06-28T23:54:17+00:00 urn:sha1:bb9b50bfcf9c656367b7a9b6b5c73fea6c21a718 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. 2016-07-28T03:26:00+00:00 Mihai Moldovan ïonic@ionic.de 2016-06-28T23:51:14+00:00 urn:sha1:6effea543d04150ca0d5aa6d4b5edadfd320ea17 Recognized values: - Strict means that the old and new default depth values must match exactly. - Safe or Risky means that the default depth values might differ, but the new default depth value must be at least as high as the former default depth value. This is recommended, because it allows clients with a higher default depth value to still connect, but not lose functionality. - Bypass or higher means that all of these checks are essentially deactivated. This is probably a very bad idea. Note that the default ReconnectTolerance value is still Strict. 2016-07-05T23:07:24+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2016-07-05T14:22:51+00:00 urn:sha1:51c3d42f3d15b181d58a0df1e5abac8d298d4484