From: L A Walsh <cygwin@tlinx.org>
To: Ken Whitesell <KenWhitesell@comcast.net>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Cygwin/X display scaling corrupting font display of typed characters;
Date: Sun, 23 Jan 2022 12:25:44 -0800 [thread overview]
Message-ID: <61EDB9C8.7000405@tlinx.org> (raw)
In-Reply-To: <61EAFAF1.9070405@tlinx.org>
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".
next prev parent reply other threads:[~2022-01-23 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 18:29 Cygwin/X with Win10 display scaling corrupting font display of typed characters Ken Whitesell
2022-01-19 0:02 ` Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified Ken Whitesell
2022-01-19 19:28 ` Jon Turney
2022-01-20 1:01 ` Ken Whitesell
2022-01-21 18:26 ` Cygwin/X with Win[10]-^ display scaling corrupting font display of typed characters - Issue [identified]-???? L A Walsh
2022-01-23 20:25 ` L A Walsh [this message]
2022-01-24 15:02 ` Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified Jon Turney
2022-01-27 3:12 ` Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified - "Solution" found Ken Whitesell
2022-02-05 14:25 ` Jon Turney
2022-08-14 11:08 ` Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61EDB9C8.7000405@tlinx.org \
--to=cygwin@tlinx.org \
--cc=KenWhitesell@comcast.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).