DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8651D3858D28
Message-ID: <61EDB9C8.7000405@tlinx.org>
Date: Sun, 23 Jan 2022 12:25:44 -0800
From: L A Walsh <cygwin@tlinx.org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: Ken Whitesell <KenWhitesell@comcast.net>
Subject: Re: Cygwin/X display scaling corrupting font display of typed
 characters; 
References: <b56c0a7e-27f3-c165-6331-69b71b2075a5@comcast.net>
 <02b8ba82-0a40-e9ea-c4e6-fe201097d957@comcast.net>
 <4f4d8d34-3e30-82fe-4be2-2926da2c1c6a@dronecode.org.uk>
 <ebef1f87-1457-3068-2657-af5dfa5c484e@comcast.net>
 <61EAFAF1.9070405@tlinx.org>
In-Reply-To: <61EAFAF1.9070405@tlinx.org>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On 2022/01/21 10:26, L A Walsh wrote:

...
To summarize, I am not sure that the original issue
has anything to do with 2nd monitor,
nor any changes in the Xorg-sources.

In _my_ case it was a matter of how the Xserver was
started, and what dpi settings it was started with.

If server was started with incorrect dpi settings, it
would cause problems with some Xclients having mangled or
trunated characters at the bottom of their windows.

For me, it was a matter of ensuring that my modified
startX script was called instead of the stock script, as
my modified script checks the windows DPI setting on startup.

That said -- on Win10 it could be further complicated
by having multiple monitors with different dpi settings.  I seem
to remember win10 having some provision for attaching a
different DPI value to different monitors.

That's likely to create a problem in 'X', since AFAIK,
X hasn't been enhanced to allow different DPI values on
different "screens".


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple