all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuuki Harano <masm+emacs@masm11.me>
To: moonsolo@gmail.com
Cc: 52042@debbugs.gnu.org
Subject: bug#52042: 29.0.50; [feature/pgtk] issue in moving a fullscreen emacs frame from a scale@1x display to a scale@2x display
Date: Thu, 02 Dec 2021 00:47:20 +0900 (JST)	[thread overview]
Message-ID: <20211202.004720.1770181195247425806.masm@luna.pink.masm11.me> (raw)
In-Reply-To: <CAOR66h=1LdSdYOUoGUuzQDuhY6RqTsHe7ZGA4WAgHK_kDSaSPw@mail.gmail.com>


On Wed, 1 Dec 2021 10:20:41 -0500,
	Fred Fu <moonsolo@gmail.com> wrote:
> How do GTK applications handle this situation?
> 
> Does each gnome app deal with their windows moving among displays of scale
> factors on their own?
> 
> Or do they just delegate the dirty job to GTK or other lower-level
> mechanisms?

Switching scale factor among display is usually done by gtk.
Usual applications create cairo_surface_t(bitmap), use it for a short
time, and destroy it.  When creating it, scaling factor is reflected.

Pgtk emacs create cairo_surface_t, use it for a long time for cost and
algorithms, and scaling factor is not reflected until recreation.

-- 
Yuuki Harano





  reply	other threads:[~2021-12-01 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOR66hntRyn0hZA_-vMhN=kGhw7x=dOxbfGJYQp-CBzX_b__mw@mail.gmail.com>
2021-11-30 15:59 ` bug#52042: 29.0.50; [feature/pgtk] issue in moving a fullscreen emacs frame from a scale@1x display to a scale@2x display Yuuki Harano
2021-11-30 16:10   ` Fred Fu
2021-12-01 15:08     ` Yuuki Harano
2021-12-01 15:20       ` Fred Fu
2021-12-01 15:47         ` Yuuki Harano [this message]
2021-12-04  7:41         ` Yuuki Harano
2021-12-02 22:09       ` Alan Third
2021-12-02 22:12         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211202.004720.1770181195247425806.masm@luna.pink.masm11.me \
    --to=masm+emacs@masm11.me \
    --cc=52042@debbugs.gnu.org \
    --cc=moonsolo@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.