unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuuki Harano <masm+emacs@masm11.me>
To: casouri@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: Which should the display-pixel-width function return, physical pixel width or logical pixel width?
Date: Sat, 02 Jan 2021 16:40:07 +0900 (JST)	[thread overview]
Message-ID: <20210102.164007.880768269147021789.masm@luna.pink.masm11.me> (raw)
In-Reply-To: <111C5580-03ED-496F-AEC7-D2C30E52B9E1@gmail.com>

Hi,

On Fri, 1 Jan 2021 16:51:21 -0500,
	Yuan Fu <casouri@gmail.com> wrote:
> As hidpi screens getting more common, we should separate pixel sizes
> reported from frontends into logical and physical pixels. This
> problem also makes images on Mac fuzzy. Currently ns frontend can
> distinct between logical and physical pixel size, from Yuuki’s post
> it seems pgtk can, too. Does other frontends have such ability?

* ns
frontend is logical.
when creating image area, its size is physical.
ns-display-monitor-attributes-list does nothing about scaling. maybe returns logical.
emacs internal is logical.

* x11+gtk
gdk frontend is logical.
x-display-monitor-attributes-list returns physical.
emacs internal is physical.

* w32
scaling is not supported.

* pgtk (current)
gdk frontend is logical.
pgtk-display-monitor-attributes-list returns logical.
emacs internal is logical.

-- 
Yuuki Harano

  reply	other threads:[~2021-01-02  7:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-01 14:44 Which should the display-pixel-width function return, physical pixel width or logical pixel width? Yuuki Harano
2021-01-01 21:51 ` Yuan Fu
2021-01-02  7:40   ` Yuuki Harano [this message]
2021-01-02 10:31     ` Alan Third
2021-01-02  6:04 ` Lars Ingebrigtsen
2021-01-03  8:34   ` Yuuki Harano

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=20210102.164007.880768269147021789.masm@luna.pink.masm11.me \
    --to=masm+emacs@masm11.me \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).