NXv3 (redistributed) https://cgit.arctica-project.org/nx-libs/atom?h=3.5.99.0 2016-06-24T22:39:26+00:00 2016-06-24T22:39:26+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2016-04-08T07:26:12+00:00 urn:sha1:8fab4afbb997f444906c09cbf3e028ead8ca1e84 Reasoning: (1) The diff between this file and mi/miwindow.c is so minimal, we simply apply the change to mi/miwindow.c. (2) In recent X.org, the fixed code has gone, so this patch won't exist after having rebased nx-libs against X.org. 2016-06-21T02:09:17+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2016-06-20T09:10:06+00:00 urn:sha1:c2b1f489d7998c83af73c7cb25bbb2bc53f26094 Backported to X.org's /xorg/xserver Git hash level: a6b6e8ba026acedef6336b17adf06aebddd5f22f. 2016-06-12T22:58:08+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2016-04-06T20:09:31+00:00 urn:sha1:f5eff9bc0a1134a16b1a6e67bfe3d0b4d7cd49e9 2016-05-02T12:53:06+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2016-03-18T04:13:43+00:00 urn:sha1:d9e7f6ae42b30e32619e1d0979598c2ba2288a3e 2015-12-29T23:05:54+00:00 Ulrich Sibiller uli42@gmx.de 2015-10-08T20:25:09+00:00 urn:sha1:c4a388937baad8215f2650d746d3ddba4d4d1ee3 This fixes the problem Mike Gabriel describes like this: - Launch a session on a system with a single monitor. Enable Xinerama for this session. - Open a desktop session in that session window (e.g. MATE or XFCE). - Move the NX/MATE-or-XFCE session window around on that one monitor. Bump at the borders, so that the session window moves into the invisible parts around your monitor. What you see is that the MATE-or-XFCE window manager will become really busy with resizing the windows and panels in the NX session, because moving the window over the physical borders of the display will trigger resize events. This is non-intuitive, I think. Same with multi-monitors on the outside edges of the physical Xorg RandR setup. 2015-12-29T23:05:53+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2015-10-07T13:17:59+00:00 urn:sha1:f1eafeaa456b1544384bb6a68d8a56c0a216a875 2015-05-20T10:16:15+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2015-05-20T09:30:05+00:00 urn:sha1:a6185abd93143524eaddd617ad2cc20a4bd198f0 2015-04-22T04:22:37+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2015-04-14T07:24:55+00:00 urn:sha1:70b77a0fc329e2e205a596a738c7307d354e7b1c 2015-04-16T15:59:18+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2015-04-14T07:42:35+00:00 urn:sha1:a5f71f084e9f32e947a04da69edb7aae96d61697 NX agent contains/ed two build trees. An old one (probably pre-3.x.y) and a "newer" one. The "newer" code tree used to become enabled by setting NXUpgradeAgentServer in nx-X11/config/cf/host.def to YES. As building the NXUpgradeAgentServer has been the default for years now, we drop all code that does not get used at build time for NXUpgradeAgentServer == YES (i.e., the code that belongs to the pre-3.x.y phase of NX agent). 2015-04-04T08:59:50+00:00 Mike Gabriel mike.gabriel@das-netzwerkteam.de 2015-03-04T12:29:02+00:00 urn:sha1:f5f280417cb0af489406c8c3234e4ad69b008c74