From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Olivier Crête" <olivier.crete@ocrete.ca>
Cc: 56832@debbugs.gnu.org
Subject: 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 [thread overview]
Message-ID: <87czdnmn0q.fsf@yahoo.com> (raw)
In-Reply-To: <b90a4b744abc2211be205fd4a2b6c306082c5cfc.camel@ocrete.ca> ("Olivier Crête"'s message of "Fri, 29 Jul 2022 13:58:42 -0400")
Olivier Crête <olivier.crete@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.
next prev parent reply other threads:[~2022-07-30 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 17:58 bug#56832: 29.0.50; Emacs pgtk started on low-DPI doesn't adapt to hi-DPI Olivier Crête
2022-07-30 1:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-31 10:17 ` Lars Ingebrigtsen
2022-08-31 11:32 ` Olivier Crête
2022-10-04 11:44 ` Lars Ingebrigtsen
2022-10-14 21:08 ` Olivier Crête
2022-10-15 9:37 ` Lars Ingebrigtsen
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=87czdnmn0q.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=56832@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=olivier.crete@ocrete.ca \
/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).