From: Alan Third <alan@idiocy.org>
To: Evgeny Zajcev <lg.zevlg@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: exposing x_get_scale_factor into elisp level
Date: Sun, 4 Apr 2021 11:38:43 +0100 [thread overview]
Message-ID: <YGmXM2k6PiB1o13w@breton.holly.idiocy.org> (raw)
In-Reply-To: <CAO=W_ZquEBqx9dJqeWYT4h2+jsXFO5c1W9AUZSe+KVcg-8Y6Ag@mail.gmail.com>
On Thu, Mar 25, 2021 at 12:20:09AM +0300, Evgeny Zajcev wrote:
> ср, 24 мар. 2021 г. в 23:27, Alan Third <alan@idiocy.org>:
>
> > On Mon, Mar 22, 2021 at 02:07:41AM +0300, Evgeny Zajcev wrote:
> > > HiDPI is very common nowadays. Internally Emacs has decent support for
> > > HiDPI displays. However elisp code, that generates non-svg images don't
> > > have any idea that logical pixel may differ from physical one, resulting
> > in
> > > generating images in low resolution on HiDPI displays.
> > >
> > > Emacs internally has a notion about HiDPI displays, such as
> > > `x_get_scale_factor`, maybe expose this function to elisp level, so
> > > packages may utilize it to generate images in highres?
> >
> > On NS platforms (macOS and GNUstep) and, I believe, native GTK the
> > scale factor is how much the TOOLKIT scales things up for display.
> >
>
> The problem we hit on MacOS is that line height is reported in logical
> pixels, and we generate PNG images using that line height value. This
> results in poor PNG quality since the physical pixel is x4 times larger.
> Now we use heavy heuristics to workaround this, it will be great to have
> some general approach as Emacs do internally (`x_get_scale_factor')
>
> Unfortunately, we can't use SVG instead of PNG at the moment
I've pushed a version of this to master, so you can use
'frame-scale-factor'.
--
Alan Third
prev parent reply other threads:[~2021-04-04 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 23:07 exposing x_get_scale_factor into elisp level Evgeny Zajcev
2021-03-24 20:27 ` Alan Third
2021-03-24 21:20 ` Evgeny Zajcev
2021-03-24 22:55 ` Alan Third
2021-03-25 1:32 ` Yuan Fu
2021-04-04 10:38 ` Alan Third [this message]
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=YGmXM2k6PiB1o13w@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=lg.zevlg@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.