unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: macOS child frame lower behavior
Date: Thu, 28 May 2020 18:54:11 +0200	[thread overview]
Message-ID: <4c0e3e63-5328-5447-ee02-762685092a5f@gmx.at> (raw)
In-Reply-To: <CAHyO48xaiYqTgxLKZGpC_E9f_J4S+SOwB7LNHYfF+M=gafXYRA@mail.gmail.com>

 > It apparently means the entire screen list on the desktop.

Sounds bad (though I have no idea what "screen list" stands for).

 > 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.

I see.  The code works here as intended with a GNUStep build (under
Debian's xfwm) so the problem is not on the Emacs side.  Does
'raise-frame' with two child frames work as intended?  What happens when
you have two overlapping child frames and you click into the lower one?
Does it raise to the top?  IIUC the following setup (which works here)
would fail: Make two normal frames A and B with A overlapping B and on B
make two child frames C and D where C overlaps D.  If you now in frame A
evaluate (raise-frame D), does as a side-effect B overlap A?

If we cannot fix that in some other way, we should probably make
lowering a child frame a NOOP on MacOS when it is the sole child frame
of its parent.  If there are two child frames, we could try to raise the
other one, if that works somehow.  For more complicated situations, we'd
have to look whether there exists a z-order for child frames and use
that.

martin



  reply	other threads:[~2020-05-28 16:54 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
2020-05-28 16:54     ` martin rudalics [this message]
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=4c0e3e63-5328-5447-ee02-762685092a5f@gmx.at \
    --to=rudalics@gmx.at \
    --cc=aaronjensen@gmail.com \
    --cc=emacs-devel@gnu.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).