From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>, Po Lu <luangruo@yahoo.com>
Cc: 74074@debbugs.gnu.org, wyuenho@gmail.com, rudalics@gmx.at
Subject: bug#74074: 30.0.92; [NS] Frame position not reported on resize from top left
Date: Wed, 06 Nov 2024 14:58:58 +0200 [thread overview]
Message-ID: <86jzdgselp.fsf@gnu.org> (raw)
In-Reply-To: <87y11wn4t2.fsf@gmail.com> (message from Robert Pluim on Wed, 06 Nov 2024 09:29:29 +0100)
> Cc: 74074@debbugs.gnu.org, martin rudalics <rudalics@gmx.at>
> From: Robert Pluim <rpluim@gmail.com>
> Date: Wed, 06 Nov 2024 09:29:29 +0100
>
> I see that under X11, the `move-frame-functions' are called when
> resizing from the top left. I donʼt know what happens on MSWindows or
> in a pgtk build.
This comes from the MOVE_FRAME_EVENT, which is triggered on Windows as
well.
Not sure about PGTK, though. Maybe Po Lu knows.
> A quick experiment shows that itʼs fixable on macOS, although there is
> a (strong) tendency for the 'moveʼ events to get bunched up until
> after the resize ends, which means they all report the same
> position. But then again this happens to a lesser extent under X as
> well.
>
> The question is: do we *want* to fix this?
What are the arguments against fixing this?
next prev parent reply other threads:[~2024-11-06 12:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 23:36 bug#74074: 30.0.92; [NS] Frame position not reported on resize from top left Jimmy Yuen Ho Wong
2024-11-06 8:29 ` Robert Pluim
2024-11-06 9:31 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-06 10:16 ` Robert Pluim
2024-11-06 12:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-06 12:58 ` Eli Zaretskii [this message]
2024-11-06 13:50 ` Robert Pluim
2024-11-06 13:59 ` Jimmy Wong
2024-11-06 14:36 ` Eli Zaretskii
2024-11-07 8:34 ` Robert Pluim
2024-11-07 18:26 ` Jimmy Wong
2024-11-07 20:13 ` Robert Pluim
2024-11-08 12:26 ` Jimmy Wong
2024-11-08 13:37 ` Robert Pluim
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=86jzdgselp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74074@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=rpluim@gmail.com \
--cc=rudalics@gmx.at \
--cc=wyuenho@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 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).