From: martin rudalics <rudalics@gmx.at>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 25511@debbugs.gnu.org, Katsumi Yamaoka <yamaoka@jpl.org>
Subject: bug#25511: 26.0.50; modify-frame-parameters modifies undesignated parameter?
Date: Mon, 23 Jan 2017 19:01:46 +0100 [thread overview]
Message-ID: <5886450A.1050002@gmx.at> (raw)
In-Reply-To: <CAM-tV-93EhBgkUakRHXWD3hjxo3jiaxfE4ZB5W703SmGy28VKg@mail.gmail.com>
> Should we change modify-frame-parameters to delay the actual
> modification until the frame turns visible?
In a sense yes, see also Bug#24526. Usually, we should be able to set
positions and sizes via the WM size hints right away so the window
manager can pick them up there whenever it maps the frame. On Windows
there is a special function to set the sizes of an invisible window.
But all this should be done independently from setting up a new frame
that is supposed to become visible immediately. In that latter case
‘modify-frame-parameters’ should not be used in the first place.
martin
prev parent reply other threads:[~2017-01-23 18:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 7:28 bug#25511: 26.0.50; modify-frame-parameters modifies undesignated parameter? Katsumi Yamaoka
2017-01-23 8:03 ` martin rudalics
2017-01-23 9:01 ` Katsumi Yamaoka
2017-01-23 10:28 ` martin rudalics
2017-01-23 22:54 ` Katsumi Yamaoka
2017-01-24 0:45 ` Katsumi Yamaoka
2017-01-24 7:46 ` martin rudalics
2017-01-24 9:18 ` Katsumi Yamaoka
2017-01-24 9:37 ` martin rudalics
2017-06-05 12:57 ` npostavs
2017-06-05 13:36 ` martin rudalics
2017-06-06 0:00 ` npostavs
2017-06-06 6:38 ` martin rudalics
2017-01-24 7:46 ` martin rudalics
2017-01-23 17:27 ` Noam Postavsky
2017-01-23 18:01 ` martin rudalics [this message]
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=5886450A.1050002@gmx.at \
--to=rudalics@gmx.at \
--cc=25511@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
--cc=yamaoka@jpl.org \
/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).