From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel 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 Message-ID: <83o9mvq2l3.fsf@gnu.org> References: <5A36B3B3.9040607@gmx.at> <5A376D9F.7000006@gmx.at> <83tvwoow4a.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1513624480 24855 195.159.176.226 (18 Dec 2017 19:14:40 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 18 Dec 2017 19:14:40 +0000 (UTC) Cc: rudalics@gmx.at, emacs-devel@gnu.org To: rswgnu@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 18 20:14:35 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eR0rz-00064U-6I for ged-emacs-devel@m.gmane.org; Mon, 18 Dec 2017 20:14:35 +0100 Original-Received: from localhost ([::1]:60452 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eR0tx-0008P5-Am for ged-emacs-devel@m.gmane.org; Mon, 18 Dec 2017 14:16:37 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60656) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eR0j5-0007RR-9C for emacs-devel@gnu.org; Mon, 18 Dec 2017 14:05:47 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eR0ip-0005Zk-Tc for emacs-devel@gnu.org; Mon, 18 Dec 2017 14:05:23 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:43245) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eR0ip-0005ZU-Nk; Mon, 18 Dec 2017 14:05:07 -0500 Original-Received: from [176.228.60.248] (port=1425 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eR0im-0003Nn-64; Mon, 18 Dec 2017 14:05:04 -0500 In-reply-to: (message from Robert Weiner on Mon, 18 Dec 2017 13:17:04 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:221222 Archived-At: > From: Robert Weiner > Date: Mon, 18 Dec 2017 13:17:04 -0500 > Cc: martin rudalics , emacs-devel > > ​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.