From: 陈宇迪 <jodieydchen@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Po Lu <luangruo@yahoo.com>,
65183@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#65183: 29.1; Child frame moving and resizing problems
Date: Fri, 11 Aug 2023 17:09:29 +0100 [thread overview]
Message-ID: <CACuMiX5OoqN6hn+Azq34V2Msb4cFJSc3YFBZYhccVvzF-QQCUg@mail.gmail.com> (raw)
In-Reply-To: <d0532509-ab78-054b-a16d-7d58205e65b2@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
I tried `(setq x-wait-for-event-timeout 0)' and ran the test function.
It was the same.
By the way, I noticed that (though I believe you have read it),
the GTK doc says "(gdk_window_move_resize) avoids strange visual effects.
i.e. the user may be able to see the window first move, then resize,
if you don’t use gdk_window_move_resize().". That is exactly what I saw.
martin rudalics <rudalics@gmx.at> 于2023年8月11日周五 11:00写道:
> > It seems that variables `x-gtk-resize-child-frames' and
> > `x-gtk-use-window-move' do not help with this.
>
> As expected.
>
> > I am using KDE with KWin (X11) version 5.27.7. I don't know where there
> is
> > any known issue on this platform.
>
> AFAICT KDE does not have any such problems.
>
> >>From another perspective, is there a way to perform resize and move at
> the
> > same time?
>
> We could try gdk_window_move_resize but we'd have to (1) investigate
> whether it works well for child frames and (2) what to do on non-GTK
> platforms.
>
> > (I mean, could the two steps be executed within a single redisplay
> cycle,
> > so that users would not see the intermediate changes?)
> > If these two steps are not done separately, the execution order would
> not
> > matter.
> > As I wrote in my first email, I can see the child frame being moved and
> > then resized
> > on my computer, even though the two steps happen very quickly.
>
> What happens when you change 'x-wait-for-event-timeout' to zero?
>
> martin
>
[-- Attachment #2: Type: text/html, Size: 2018 bytes --]
next prev parent reply other threads:[~2023-08-11 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 14:28 bug#65183: 29.1; Child frame moving and resizing problems 陈宇迪
2023-08-10 8:55 ` Eli Zaretskii
[not found] ` <CACuMiX6AnPcrhPOni-jgr5NmJ9-qG5UXCE5cFB_vN8b2OLZcjQ@mail.gmail.com>
2023-08-10 17:31 ` Eli Zaretskii
2023-08-11 7:06 ` martin rudalics
2023-08-11 8:01 ` 陈宇迪
2023-08-11 10:00 ` martin rudalics
2023-08-11 16:09 ` 陈宇迪 [this message]
2023-08-12 0:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-12 7:00 ` martin rudalics
2023-08-12 6:52 ` martin rudalics
2023-08-12 13:55 ` 陈宇迪
2023-08-13 7:21 ` martin rudalics
2023-08-13 13:34 ` 陈宇迪
2023-08-15 6:38 ` martin rudalics
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=CACuMiX5OoqN6hn+Azq34V2Msb4cFJSc3YFBZYhccVvzF-QQCUg@mail.gmail.com \
--to=jodieydchen@gmail.com \
--cc=65183@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=rudalics@gmx.at \
/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).