From: Alan Third <alan@idiocy.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 28512-done@debbugs.gnu.org
Subject: bug#28512: 26.0.60; undecorated frames on macOS 10.13 do not resize properly
Date: Thu, 23 Dec 2021 16:09:24 +0000 [thread overview]
Message-ID: <YcSfNCn5pvB65Eak@breton.holly.idiocy.org> (raw)
In-Reply-To: <CAHyO48yk4LJRvRh71hhgnDHemsfAK-ci8V4SHwqN9sCiKpn2ug@mail.gmail.com>
On Thu, Dec 23, 2021 at 10:20:40AM -0500, Aaron Jensen wrote:
> On Wed, Dec 22, 2021 at 3:52 PM Alan Third <alan@idiocy.org> wrote:
> >
> > Aaron Jensen <aaronjensen@gmail.com> writes:
> >
> > > On Sun, Jul 25, 2021 at 7:17 AM Alan Third <alan@idiocy.org> wrote:
> > >>
> > >> Hi Aaron,
> > >>
> > >> if you're still interested in this I've got a preliminary implementation
> > >> of the recreate-the-frame setup in the scratch/ns/refactor branch.
> > >>
> > >> I've not changed the flags to make borderless frames resizable, but it
> > >> should be a simple change.
> > >
> > > Thanks, I'm sticking with a title bar for now, but maybe I'll give it
> > > a shot some time.
> >
> > I've pushed this change now and will mark this as done.
>
> Thanks. I'm out of context on this change now, but it looks like now
> that this change has merged all undecorated frames have a shadow,
> which I guess is what macOS gives resizable frames. I don't know if I
> mind it yet, but is there a frame-parameter that would turn that off?
Looks like we can set hasShadow to NO. Maybe we want to do that to
undecorated child frames, or something?
--
Alan Third
next prev parent reply other threads:[~2021-12-23 16:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 15:10 bug#28512: 26.0.60; undecorated frames on macOS 10.13 do not resize properly Aaron Jensen
2017-09-19 15:35 ` Aaron Jensen
2017-09-19 21:34 ` Alan Third
2017-09-19 21:44 ` Aaron Jensen
2017-09-23 14:31 ` Aaron Jensen
2017-09-23 19:11 ` Alan Third
2017-09-23 21:35 ` Aaron Jensen
2017-09-24 11:27 ` Alan Third
2017-09-24 15:43 ` Aaron Jensen
2017-09-24 21:05 ` Alan Third
2017-09-25 0:39 ` Aaron Jensen
2017-09-25 10:13 ` Alan Third
2017-09-25 15:18 ` Aaron Jensen
2017-09-25 16:33 ` Alan Third
2017-09-25 17:02 ` Aaron Jensen
2017-10-14 21:47 ` Aaron Jensen
2017-10-16 10:01 ` Alan Third
2017-10-16 12:49 ` Aaron Jensen
2017-10-16 20:46 ` Alan Third
2017-10-17 2:50 ` Aaron Jensen
2017-10-17 8:58 ` Alan Third
2017-10-18 16:08 ` Aaron Jensen
2017-10-18 16:12 ` Aaron Jensen
2017-10-18 19:32 ` Alan Third
2017-10-18 19:50 ` Alan Third
2017-10-19 1:00 ` Aaron Jensen
2021-07-25 11:17 ` Alan Third
2021-07-25 17:06 ` Aaron Jensen
2021-12-22 20:52 ` Alan Third
2021-12-23 15:20 ` Aaron Jensen
2021-12-23 16:09 ` Alan Third [this message]
2021-12-23 18:19 ` Aaron Jensen
2021-12-28 11:43 ` Alan Third
2021-12-28 16:18 ` Aaron Jensen
2022-01-04 10:58 ` Alan Third
2017-10-17 8:59 ` martin rudalics
2017-10-17 16:06 ` 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=YcSfNCn5pvB65Eak@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=28512-done@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
/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).