GNU bug report logs - #53793
29.0.50; 'fullscreen' frame parameter on pgtk

Previous Next

Full log

Message #16 received at 53793-done <at> debbugs.gnu.org (full text, mbox):

From: Augusto Stoffel <arstoffel <at> gmail.com>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 53793-done <at> debbugs.gnu.org
Subject: Re: bug#53793: 29.0.50; 'fullscreen' frame parameter on pgtk
Date: Sun, 06 Feb 2022 11:02:19 +0100

On Sun,  6 Feb 2022 at 17:38, Po Lu <luangruo <at> yahoo.com> wrote:

> (When replying to bug reports in the future, please use "Reply to All",
> so that your messages can be recorded by the bug tracker.)

Oops, sorry.

> Augusto Stoffel <arstoffel <at> gmail.com> writes:
>
>> Yes, the frame parameter is correctly reported now, thanks!
>
> I'm closing this bug then, thanks.
>
>> It also seems that `move-frame-functions' are not run as promised.  Or
>> at least the following bit of configuration is still broken on pgtk but
>> works fine on X.
>
> If you're running Wayland, then it's a limitation of the Wayland
> protocol, which has no global coordinate system.  GTK exposes it as
> every Wayland window (surface) being placed at 0, 0.

I see.  Apparently there's no hook to run when a frame is resized, which
would be useful as well.  Maybe a new variable is unnecessary, and
`move-frame-functions' should be run also when moving the bottom right
corner of the frame.

>>     (add-hook 'move-frame-functions
>>               (lambda (frame) "Undecorate frame when maximized."
>>                 (set-frame-parameter frame 'undecorated
>>                  (eq 'maximized (frame-parameter frame 'fullscreen)))))

Previous Next

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