unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Wed, 24 Mar 2021 20:27:11 +0000	[thread overview]
Message-ID: <YFugn0++TRGv+C/X@breton.holly.idiocy.org> (raw)
In-Reply-To: <CAO=W_Zrs5GM2DzZbQEzWmDXc1zVBPM76-ckd1t-D1nXNEHXNPQ@mail.gmail.com>

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.

But on plain X it's actually how much YOU have to scale things up to
get to "logical" pixels. Emacs on X only uses the logical sizes for
the toolbar and possibly some other window chrome, and then only on
GTK builds.

I couldn't work out how to reconcile the two approaches, and didn't
actually need it for the SVG work, so I forgot about it. It may make
sense to just ignore this stuff on X once we have PGTK merged.

Windows appears to be completely different, providing some three or
four different approaches to HiDPI.
-- 
Alan Third



  reply	other threads:[~2021-03-24 20:27 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 [this message]
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

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=YFugn0++TRGv+C/X@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 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).