From: Robert Pluim <rpluim@gmail.com>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: 37770@debbugs.gnu.org
Subject: bug#37770: [PATCH] Expose scale factor through the redisplay interface
Date: Thu, 24 Oct 2019 11:19:24 +0200 [thread overview]
Message-ID: <m27e4usdpf.fsf@gmail.com> (raw)
In-Reply-To: <CAELgYhe_1gz_=KMEYhJBKzUZW_cQS1rNHF=NZ_5HS117se=5Ew@mail.gmail.com> (Carlos Pita's message of "Tue, 22 Oct 2019 15:06:49 -0300")
>>>>> On Tue, 22 Oct 2019 15:06:49 -0300, Carlos Pita <carlosjosepita@gmail.com> said:
Carlos> I've improved the code comment for the redisplay interface entry in:
Carlos> https://github.com/memeplex/emacs/commit/d3c66e6eea8a3b6f1a269bd968597a3bd8a3e811
Carlos> (to generate the patch, add a .patch suffix to that url)
Carlos> The new comment states:
Carlos> /* Return the scale factor for the screen containing frame F. All
Carlos> geometries are reported by the backend using a scale that is
Carlos> approximately 96dpi x scale_factor. This scale may match
Carlos> physical resolution or not. */
Two spaces after '.'. Also: "This scale may not match the physical resolution."
Carlos> Some thoughts:
Carlos> One possibility for the (maybe distant) future, is that this scale
Carlos> factor api won't be needed any more. Like nsterm does (I believe), all
Carlos> backends might expose a 1 x 96dpi interface so that the upper layers
Carlos> can work mostly or fully unaware of the device complexities. But at
Carlos> this moment the xterm backend goes to lengths in order to revert gtk
Carlos> auto-scaling and provide a "physical dpi" (well, not necessarily
Carlos> physical, since there is still randr in the middle) interface to the
Carlos> upper layers, thus losing the benefits of gtk auto-scaling, although
Carlos> with good reason since nowadays gtk is more of a hack to the x11
Carlos> backend, sniffing the underlying x event loop as it is, than a proper
Carlos> backend on its own.
If emacs used only GTK to draw things to the screen, then indeed there
would be no need for those conversions, as GTK would handle them.
<https://github.com/masm11/emacs> is attempting to implement a 'pure'
GTK backend. I have no idea how close it is to being ready to merge.
Carlos> Anyway, even if that's not the trend, exposing a higher scale factor
Carlos> to the upper layers still has the potential benefit of letting those
Carlos> layers decide how to better use the extra available resolution,
Carlos> instead of pretending they are drawing to a vintage screen. Whether
Carlos> this is worthwhile or not I don't know, given that font and image
Carlos> rendering are the parts most profited from this extra resolution, and
Carlos> that fact every modern toolkit already exploits. In any case, at this
Carlos> moment we still need the api because of the differences between
Carlos> backends.
Youʼre right about that (although on macOS we seem to get by OK
without it).
Robert
next prev parent reply other threads:[~2019-10-24 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 22:29 bug#37770: [PATCH] Expose scale factor through the redisplay interface Carlos Pita
2019-10-16 0:32 ` Carlos Pita
2019-10-16 8:51 ` Robert Pluim
2019-10-16 16:12 ` Carlos Pita
2019-10-16 19:08 ` Carlos Pita
2019-10-17 8:01 ` Robert Pluim
2019-10-20 12:34 ` Eli Zaretskii
2019-10-20 17:22 ` Carlos Pita
2019-10-22 18:06 ` Carlos Pita
2019-10-24 9:19 ` Robert Pluim [this message]
2019-10-24 14:34 ` Carlos Pita
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m27e4usdpf.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=37770@debbugs.gnu.org \
--cc=carlosjosepita@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).