From: Eli Zaretskii <eliz@gnu.org>
To: "J. Scott Berg" <jsberg-bnl@outlook.com>,
martin rudalics <rudalics@gmx.at>
Cc: 44002@debbugs.gnu.org
Subject: bug#44002: 27.1; Small window height with VcXsrv X server when built with gtk3 toolkit
Date: Sat, 17 Oct 2020 10:52:29 +0300 [thread overview]
Message-ID: <83y2k5thky.fsf@gnu.org> (raw)
In-Reply-To: <MN2PR12MB46066998FD355F2C3DB2AC599A030@MN2PR12MB4606.namprd12.prod.outlook.com> (jsberg-bnl@outlook.com)
> From: "J. Scott Berg" <jsberg-bnl@outlook.com>
> Date: Fri, 16 Oct 2020 23:29:09 +0000
>
> I did a bit more debugging. What seems to be happening is that we receive a pair of ConfigureNotify events in rapid succession. The first is for the top level window, and has a reasonable width and height. The second is for the window associated with the frame, but it has a width=1 height=1. This then leads to the resizing of the frame. Presumably the frame's window is not yet mapped, and thus the bogus width and height. Checking for visibility on the frame fixes the problem. I've attached a patch that works for me, but I haven't exhaustively tested all the various possible cases.
Thanks.
Martin, any comments on the proposed patch? Or on the problem in
general?
Btw, do we understand why this happens only with VcXsrv?
next prev parent reply other threads:[~2020-10-17 7:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 1:55 bug#44002: 27.1; Small window height with VcXsrv X server when built with gtk3 toolkit J. Scott Berg
2020-10-16 7:31 ` Eli Zaretskii
2020-10-16 14:47 ` J. Scott Berg
2020-10-16 19:08 ` Eli Zaretskii
2020-10-16 19:47 ` J. Scott Berg
2020-10-16 23:29 ` J. Scott Berg
2020-10-17 7:52 ` Eli Zaretskii [this message]
2020-10-17 9:32 ` martin rudalics
2020-10-17 9:34 ` Eli Zaretskii
2020-10-17 9:40 ` martin rudalics
2020-10-17 17:32 ` Eli Zaretskii
2020-10-18 17:52 ` Robert Pluim
2020-10-18 17:56 ` Eli Zaretskii
2020-10-19 8:15 ` Robert Pluim
2021-02-25 20:04 ` Glenn Morris
2021-02-25 20:28 ` J. Scott Berg
2021-02-25 20:38 ` Eli Zaretskii
2020-10-19 14:02 ` J. Scott Berg
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=83y2k5thky.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44002@debbugs.gnu.org \
--cc=jsberg-bnl@outlook.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).