From: Csaba Raduly <rcsaba@gmail.com>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: cygwin install blurry on high dpi Windows 10
Date: Fri, 29 May 2020 21:37:49 +0200 [thread overview]
Message-ID: <CAEhDDbAQjNL3Zn7zrG1-ni8D9hLfiBgtKbaUVKW8DMBACrs+YA@mail.gmail.com> (raw)
In-Reply-To: <da377199-a8df-c6ca-5df8-918c973b3587@dronecode.org.uk>
On Fri, May 29, 2020 at 7:16 PM Jon Turney wrote:
>
> On 27/05/2020 12:41, Sharuzzaman Ahmat Raslan via Cygwin wrote:
> > Hi,
> >
> > My office laptop is Windows 10 with a high DPI display.
> >
> > I found that the installer is blurry, especially inside the window. The
> > title of the window is clear.
> >
> > Is this something that has been reported before? If nobody has reported it,
> > then I would like to report the issue here.
>
> Thanks for reporting this issue.
>
> This is Windows doing "dpi virtualization" (it reports 96 dpi to the
> app, and then upscales what it draws to the actual dpi)
>
> Since we (now) use standard UI elements for everything in setup, it
> should 'just' be a case of marking setup as being able to handle being
> told the real dpi.
>
> I built an updated setup with that change:
>
> https://cygwin.com/setup/setup-2.904-4-gaa071e.x86_64.exe
> https://cygwin.com/setup/setup-2.904-4-gaa071e.x86.exe
>
Thank you very much. I was waiting for this to happen.
Here's a before-and-after comparison:
https://imgur.com/a/nawlvNd
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformant way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
next prev parent reply other threads:[~2020-05-29 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 11:41 Sharuzzaman Ahmat Raslan
2020-05-29 16:05 ` Jon Turney
2020-05-29 16:32 ` Thomas Wolff
2020-06-02 21:28 ` Jon Turney
2020-05-29 19:37 ` Csaba Raduly [this message]
2020-06-02 21:28 ` Jon Turney
2020-06-01 8:50 ` Sharuzzaman Ahmat Raslan
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=CAEhDDbAQjNL3Zn7zrG1-ni8D9hLfiBgtKbaUVKW8DMBACrs+YA@mail.gmail.com \
--to=rcsaba@gmail.com \
--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).