unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Aaron Jensen <aaronjensen@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: macOS child frame lower behavior
Date: Thu, 28 May 2020 09:00:53 -0700	[thread overview]
Message-ID: <CAHyO48xaiYqTgxLKZGpC_E9f_J4S+SOwB7LNHYfF+M=gafXYRA@mail.gmail.com> (raw)
In-Reply-To: <51315ef4-9528-c0bd-51c8-4484dd44a8da@gmx.at>

On Thu, May 28, 2020 at 12:04 AM martin rudalics <rudalics@gmx.at> wrote:
>    Moves the window to the back of its level in the screen list, without
>    changing either the key window or the main window.
>
> it should but that depends on what "level on the screen list" precisely
> means.

It apparently means the entire screen list on the desktop. If you
lower a child frame, the only way to actually lower it (because it's
attached to the stacking context of the parent) is to lower the
parent, or so macOS thinks.

> If it doesn't do the same, we likely have a bug but I cannot check that
> here.  Maybe you can try to find out what ns_lower_frame does on your
> system.

It appears to do what Emacs is doing, which is the incorrect
behavior--it hides the parent window. Here's a minimal repro without
Emacs:

https://github.com/aaronjensen/child-frame-order-back-repro

>  And maybe you can tell us whether 'ns-frame-restack' behaves as
> documented too.

AFAICT, at least in Emacs, it does not do what is described. I created
two child frames and attempted to restack them so that the second
created one was above the first. This seemed to have no effect.


Aaron



  reply	other threads:[~2020-05-28 16:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28  1:34 macOS child frame lower behavior Aaron Jensen
2020-05-28  7:04 ` martin rudalics
2020-05-28 16:00   ` Aaron Jensen [this message]
2020-05-28 16:54     ` martin rudalics
2020-05-29  0:16       ` Aaron Jensen
2020-05-29  6:45         ` martin rudalics
2020-05-30 20:39           ` Aaron Jensen

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='CAHyO48xaiYqTgxLKZGpC_E9f_J4S+SOwB7LNHYfF+M=gafXYRA@mail.gmail.com' \
    --to=aaronjensen@gmail.com \
    --cc=emacs-devel@gnu.org \
    --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).