From: Thomas Wolff <towo@towo.net>
To: cygwin-announce@cygwin.com
Subject: Updated: mintty 2.4.3 and test release mintty 2.5.0
Date: Tue, 23 Aug 2016 09:04:00 -0000 [thread overview]
Message-ID: <57BB8AE3.9000703@towo.net> (raw)
I have uploaded mintty 2.4.3 with the following changes:
* Fix trails when moving other window over mintty under certain
conditions (#576).
* Fix format of double child creation error message.
I have also uploaded mintty 2.5.0 as a test release with the following
change:
* Revise DPI handling (#470; #492, #487); always consider individual
monitor DPI.
Note that this release introduces a slightly incompatible change in mintty.
The issue is that the interpretation of font size used to be suitable
for traditional resolution monitors and did not consider higher-DPI
monitors or the Windows monitor "zooming" feature which adjusts a
virtual DPI.
As a result, the handling of changed DPI (when moving the window to
another monitor) introduced in 2.2.1 interfered with other aspects, the
initial DPI was not considered, and a number of unpleasant side effects
were occasionally observed.
I intend to change DPI handling to be consistent with the respective
monitor DPI (as optionally configured by "zooming factor"), and to
comply with font size interpreation of other applications, e.g. notepad.
In consequence the initial font size may be smaller (or larger) than
before, depending on the actual monitor geometry and configuration.
Nothing would change on a "standard" monitor configuration. To
compensate, some people may have to change their font size configuration.
The homepage is at http://mintty.github.io/
It also links to the issue tracker.
------
Thomas
reply other threads:[~2016-08-23 9:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=57BB8AE3.9000703@towo.net \
--to=towo@towo.net \
--cc=cygwin-announce@cygwin.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).