From: martin rudalics <rudalics@gmx.at>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: David Reitter <david.reitter@gmail.com>,
Stefan Monnier <monnier@IRO.UMontreal.CA>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Frame ordering
Date: Mon, 14 Jun 2010 10:24:24 +0200 [thread overview]
Message-ID: <4C15E738.10204@gmx.at> (raw)
In-Reply-To: <wlhbl62hj9.wl%mituharu@math.s.chiba-u.ac.jp>
> At least Cocoa AppKit selects the foremost one just as we expect,
> without the necessity of specifying the window that shall be shown.
> That's the behavior of Emacs 22 Carbon+AppKit port and Emacs 23 Mac
> port. As far as I tested, many X11 window managers also behave like
> this. Only the NS port doesn't for some reason.
It would be interesting to know whether the NS port "buries" the
foremost Emacs window at the time it selects another one (or creates a
new one). That is, if you have at least four Emacs frames and delete
them one by one, how does the other frame shown relate to the order in
which frames were created or changed their position in the Z-order.
Also, in delete_frame we have to select another frame in case the deleted
frame is the selected one. Next comes:
#ifdef NS_IMPL_COCOA
else
/* Under NS, there is no system mechanism for choosing a new
window to get focus -- it is left to application code.
So the portion of THIS application interfacing with NS
needs to know about it. We call Fraise_frame, but the
purpose is really to transfer focus. */
Fraise_frame (frame1);
#endif
before we do switch frames. Is this related to the issue at hand?
martin
next prev parent reply other threads:[~2010-06-14 8:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E9FAA849-1E93-4DD7-AE9D-5E644D990202@univie.ac.at>
2010-06-11 12:29 ` Frame ordering David Reitter
2010-06-11 13:22 ` martin rudalics
2010-06-11 13:55 ` David Reitter
2010-06-11 17:13 ` martin rudalics
2010-06-11 21:04 ` David Reitter
2010-06-12 8:01 ` martin rudalics
2010-06-13 20:16 ` David Reitter
2010-06-14 0:30 ` Stefan Monnier
2010-06-14 2:42 ` David Reitter
2010-06-14 3:30 ` YAMAMOTO Mitsuharu
2010-06-14 6:50 ` martin rudalics
2010-06-14 6:55 ` Lennart Borgman
2010-06-14 7:35 ` YAMAMOTO Mitsuharu
2010-06-14 8:24 ` martin rudalics [this message]
2010-06-14 8:31 ` YAMAMOTO Mitsuharu
2010-06-14 9:20 ` martin rudalics
2010-06-14 9:28 ` YAMAMOTO Mitsuharu
2010-06-14 13:29 ` Stefan Monnier
2010-06-14 3:52 ` YAMAMOTO Mitsuharu
2010-06-14 15:52 ` David Reitter
2010-06-14 16:05 ` Lennart Borgman
2010-06-14 16:29 ` David Reitter
2010-06-14 16:47 ` Lennart Borgman
2010-06-14 17:10 ` Jan Djärv
2010-06-14 17:15 ` Lennart Borgman
2010-06-14 17:14 ` David Reitter
2010-06-14 17:19 ` Lennart Borgman
2010-06-14 18:49 ` Stefan Monnier
2010-06-15 3:54 ` David Reitter
2010-06-15 13:25 ` Stefan Monnier
2010-06-15 14:33 ` David Reitter
2010-06-15 9:24 ` YAMAMOTO Mitsuharu
2010-06-14 6:50 ` martin rudalics
2010-06-12 4:12 ` David Reitter
2010-06-12 5:42 ` YAMAMOTO Mitsuharu
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=4C15E738.10204@gmx.at \
--to=rudalics@gmx.at \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
--cc=monnier@IRO.UMontreal.CA \
/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).