X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org 8651D3858D28
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=tlinx.org
Authentication-Results:	sourceware.org; spf=pass smtp.mailfrom=tlinx.org
Message-ID:	<61EDB9C8.7000405@tlinx.org>
Date:	Sun, 23 Jan 2022 12:25:44 -0800
From:	L A Walsh <cygwin AT tlinx DOT org>
User-Agent:	Thunderbird
MIME-Version:	1.0
To:	Ken Whitesell <KenWhitesell AT comcast DOT net>
Subject:	Re: Cygwin/X display scaling corrupting font display of typed
	characters;
References:	<b56c0a7e-27f3-c165-6331-69b71b2075a5 AT comcast DOT net>
	<02b8ba82-0a40-e9ea-c4e6-fe201097d957 AT comcast DOT net>
	<4f4d8d34-3e30-82fe-4be2-2926da2c1c6a AT dronecode DOT org DOT uk>
	<ebef1f87-1457-3068-2657-af5dfa5c484e AT comcast DOT net>
	<61EAFAF1 DOT 9070405 AT tlinx DOT org>
In-Reply-To:	<61EAFAF1.9070405@tlinx.org>
X-Spam-Status:	No, score=-1.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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 AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Cc:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT 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

- Raw text -