From: martin rudalics <rudalics@gmx.at>
To: Alan Third <alan@idiocy.org>
Cc: Aaron Jensen <aaronjensen@gmail.com>, 28872@debbugs.gnu.org
Subject: bug#28872: 26.0.90; non-native-fullscreen does not play well with ns-transparent-titlebar on macOS
Date: Tue, 31 Oct 2017 09:40:30 +0100 [thread overview]
Message-ID: <59F836FE.8080302@gmx.at> (raw)
In-Reply-To: <20171028131127.GA70513@breton.holly.idiocy.org>
> What are original-width and original-height used for?
Maybe the terms ‘normal-width’ and ‘normal-height’ would be better.
They would be used for storing the width and height of the "normal" (not
maximized, fullscreen) frame. Currently, we store as width and height
the current size of the frame even if it is, for example, maximized.
Manipulating the width or height will then resize the frame although,
conceptually it should remain maximized.
Some window systems allow to set the normal frame size while a frame is
maximized without actually changing the frame size. Demaximizing the
frame would then use that new size instead of restoring the frame to the
size it had before maximizing it. I'm not sure whether we can do that
on all our platforms though.
martin
prev parent reply other threads:[~2017-10-31 8:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 3:00 bug#28872: 26.0.90; non-native-fullscreen does not play well with ns-transparent-titlebar on macOS Aaron Jensen
2017-10-17 14:25 ` Alan Third
2017-10-19 1:08 ` Aaron Jensen
2017-10-19 11:17 ` Alan Third
[not found] ` <CAHyO48y5jy7L7E+BZTtTAtd5eGcUb-W54FQXhfEh444WPx4j3A@mail.gmail.com>
2017-10-25 13:38 ` Alan Third
2017-10-25 15:15 ` Aaron Jensen
2017-10-28 13:19 ` Alan Third
2017-10-28 17:15 ` Aaron Jensen
2017-10-28 17:17 ` Aaron Jensen
2017-11-05 18:59 ` Alan Third
2017-10-26 7:56 ` martin rudalics
2017-10-28 13:11 ` Alan Third
2017-10-31 8:40 ` martin rudalics [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59F836FE.8080302@gmx.at \
--to=rudalics@gmx.at \
--cc=28872@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=alan@idiocy.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.