From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sa-prd-fep-044.btinternet.com (mailomta19-sa.btinternet.com [213.120.69.25]) by sourceware.org (Postfix) with ESMTPS id 9A16A385840A for ; Thu, 4 Nov 2021 14:10:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 9A16A385840A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dronecode.org.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=dronecode.org.uk Received: from sa-prd-rgout-002.btmx-prd.synchronoss.net ([10.2.38.5]) by sa-prd-fep-044.btinternet.com with ESMTP id <20211104141014.YQSW24689.sa-prd-fep-044.btinternet.com@sa-prd-rgout-002.btmx-prd.synchronoss.net>; Thu, 4 Nov 2021 14:10:14 +0000 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com; bimi=skipped X-SNCR-Rigid: 6139417C083CD6B4 X-Originating-IP: [81.129.146.209] X-OWM-Source-IP: 81.129.146.209 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvuddrtdeggdehjecutefuodetggdotefrodftvfcurfhrohhfihhlvgemuceutffkvffkuffjvffgnffgvefqofdpqfgfvfenuceurghilhhouhhtmecufedtudenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomheplfhonhcuvfhurhhnvgihuceojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukheqnecuggftrfgrthhtvghrnhepvddtteffkeevveejgeehgeelhfdtgefgieelgffgudetudefvdeggfeiiefftdevnecukfhppeekuddruddvledrudegiedrvddtleenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddruddtfegnpdhinhgvthepkedurdduvdelrddugeeirddvtdelpdhmrghilhhfrhhomhepjhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukhdprhgtphhtthhopegthihgfihinhestgihghifihhnrdgtohhmpdhrtghpthhtohepmhhoshhssegtshdruhhmrghsshdrvgguuh X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.103] (81.129.146.209) by sa-prd-rgout-002.btmx-prd.synchronoss.net (5.8.716.04) (authenticated as jonturney@btinternet.com) id 6139417C083CD6B4; Thu, 4 Nov 2021 14:10:14 +0000 Message-ID: Date: Thu, 4 Nov 2021 14:10:09 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: Confusing Cygwin X / xlaunch issue Content-Language: en-GB To: moss@cs.umass.edu, The Cygwin Mailing List References: <1e4edecf-166c-e3c1-f961-b31bfa01271f@cs.umass.edu> From: Jon Turney In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1191.1 required=5.0 tests=BAYES_00, FORGED_SPF_HELO, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, LIKELY_SPAM_BODY, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_PASS, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2021 14:10:18 -0000 On 26/10/2021 16:38, Eliot Moss wrote: > On 10/26/2021 4:02 PM, Jon Turney wrote: >> On 24/10/2021 12:01, Eliot Moss wrote: >>> First, things work fine when I am using just my hi-res laptop >>> display, or that >>> display plus a hi-res external display in "Extend these displays" mode >>> according to Windows 10.  At present I am using a lower resolution >>> external >>> display (becaue I am on an extended trip and it's what I have) in >>> "Extend >>> these displays" mode with my hi-res laptop display.  This seems to >>> confuse X >>> (and also xlaunch?).  Here are the issues: >> >> Thanks for reporting this problem. > >>> When booted with the external lo-res display as the main display: >>> >>> - xterm windows come up with a very large font. >>> - The X menu (controlled by .XWinrc) does not come up. >> >> This means that you're right-clicking on the notification area icon, >> but no menu appears? > > Correct. > >> If so, I guess this means that we're getting confused about where to >> place the menu, but I'm not sure how that could happen. > >> wrt the font scaling issue, looking at the source, it seems that we >> don't re-consider the display dpi after a WM_DISPLAYCHANGE message, >> but keep on using the value determined at startup.  This is probably a >> bug. I've made an attempt at fixing this in the xserve 21.1.0-1 test release. The X server should now be aware of Windows DPI changes (only on the primary monitor at the moment), and update the X screen information (and probably emit some kind of xrandr event, which X applications may take note of or not...) (Advertising this awareness also stops Windows from always reporting to it the DPI when it started, and rescaling windows when it changes or they move between monitors with different DPI values (which could lead to some blurriness)) Perhaps you could try that, and see if it improves things for you? -- Jon Turney Volunteer Cygwin/X X Server maintainer