unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rswgnu@gmail.com
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: display-until.el - Display a window or frame topmost in the frame stack until a condition or timeout occurs
Date: Mon, 18 Dec 2017 21:05:12 +0200	[thread overview]
Message-ID: <83o9mvq2l3.fsf@gnu.org> (raw)
In-Reply-To: <CA+OMD9h0p8+kkToDGH_BB+2haBffbccUCLWGaMVwrShdzX=VOQ@mail.gmail.com> (message from Robert Weiner on Mon, 18 Dec 2017 13:17:04 -0500)

> From: Robert Weiner <rsw@gnu.org>
> Date: Mon, 18 Dec 2017 13:17:04 -0500
> Cc: martin rudalics <rudalics@gmx.at>, emacs-devel <emacs-devel@gnu.org>
> 
> ​If possible, shouldn't make-frame wait until the frame is
> created and mapped to the display if the creation command
> demands mapping?  I guess you could start editing properties
> on ​an as yet unmapped frame but in the general case, wouldn't
> a programmer want the frame and its constituent parts to
> exist prior to moving on?
> 
> Since frame creation is done by a separate thread now,
> are all following operations on the frame queued until the
> whole frame is built or will they be lost if invoked during
> this interim creation period.  For example, if I change an
> item on the toolbar prior to full toolbar creation, what
> happens?

AFAIK, you can operate on the frame, as long as you don't expect it to
be displayed right away.

> How can an Elisp programmer be sure the frame creation has
> finished without any reference to its creation thread?

The usual way is to insert

  (sit-for 0 t)

before the code that needs the frame visible.  You can see this, e.g.,
in fancy-splash-frame and in some other places.




  reply	other threads:[~2017-12-18 19:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-17 17:28 display-until.el - Display a window or frame topmost in the frame stack until a condition or timeout occurs Robert Weiner
2017-12-17 18:13 ` martin rudalics
2017-12-17 18:46   ` Robert Weiner
2017-12-18  7:26     ` martin rudalics
2017-12-18 16:10       ` Eli Zaretskii
2017-12-18 18:17         ` Robert Weiner
2017-12-18 19:05           ` Eli Zaretskii [this message]
2017-12-18 19:19             ` Robert Weiner
2017-12-19 17:05               ` Eli Zaretskii
2018-01-02 17:36                 ` Robert Weiner
2017-12-20  8:54       ` martin rudalics
2017-12-20 13:44         ` Robert Weiner
2018-01-02 17:38         ` Robert Weiner
2018-01-07 16:08           ` martin rudalics
2018-01-16 17:06             ` Robert Weiner
2018-01-19 18:55         ` martin rudalics
2018-01-20  5:12           ` Noam Postavsky
2018-01-20 10:34             ` 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=83o9mvq2l3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rswgnu@gmail.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).