GNU bug report logs - #56832
29.0.50; Emacs pgtk started on low-DPI doesn't adapt to hi-DPI

Previous Next

Package: emacs;

Reported by: Olivier Crête <olivier.crete <at> ocrete.ca>

Date: Fri, 29 Jul 2022 18:27:01 UTC

Severity: normal

Tags: moreinfo

Found in version 29.0.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #8 received at 56832 <at> debbugs.gnu.org (full text, mbox):

From: Po Lu <luangruo <at> yahoo.com>
To: Olivier Crête <olivier.crete <at> ocrete.ca>
Cc: 56832 <at> debbugs.gnu.org
Subject: Re: bug#56832: 29.0.50; Emacs pgtk started on low-DPI doesn't adapt
 to hi-DPI
Date: Sat, 30 Jul 2022 09:01:41 +0800
Olivier Crête <olivier.crete <at> ocrete.ca> writes:

> Hi,
>
> If I start emacs on my low DPI screen (a normal 1080p screen), when I
> switch it to another screen which is 4K, it doesn't adapt correctly but
> instead I get the blurry scaling from the compositor. I'd expect it to
> listen to the appropriate Wayland events and change its internal
> scaling factor.
>
> This is all using master built with pgtk (from the copr).

Could you please put a breakpoint here:

static void
update_watched_scale_factor (struct atimer *timer)
{
  struct frame *f = timer->client_data;
  double scale_factor = FRAME_SCALE_FACTOR (f);

  if (scale_factor != FRAME_X_OUTPUT (f)->watched_scale_factor)
    {
      FRAME_X_OUTPUT (f)->watched_scale_factor = scale_factor;
      pgtk_cr_update_surface_desired_size (f,
					   FRAME_CR_SURFACE_DESIRED_WIDTH (f),
====>					   FRAME_CR_SURFACE_DESIRED_HEIGHT (f),
					   true);
    }
}

with the following commands:

  p scale_factor
  c

and see if it is ever called, and what the value scale_factor is, once
you move the frame to the other monitor.

Thanks.




This bug report was last modified 2 years and 221 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.