From: David Reitter <david.reitter@gmail.com>
To: Anders Lindgren <andlind@gmail.com>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: recent change to nsterm.m: four pixels where the Dock is hidden
Date: Thu, 24 Mar 2016 22:59:39 -0400 [thread overview]
Message-ID: <25AFEF78-9B39-41F1-BC01-0208500E2711@gmail.com> (raw)
Anders,
I appreciate your work on the NS/OSX port.
Reviewing a recent change, I can’t help but wonder: Do we really need 50 lines of a hack to counteract design decisions made at the system level?
If [NSScreen visibleFrame] tells us not to occupy certain space on the screen - four pixels where the Dock is hidden - then that’s a standard that all applications should adhere to. It’s probably done for a reason (such as being able to un-hide the Dock and to grab the lower horizontal edge of the window for resizing).
ns_screen_margins_ignoring_hidden_dock is, excuse my bluntness, ugly as it hardcodes some numbers that can change any time with a new OS version. It’s a burden for future maintenance.
If this is what #22988 really was about, then it’s not a bug and we shouldn’t mess with it. Also not in 25.1.
If I’m wrong, please excuse me. Could you explain if there is some deeper reasoning that I’m missing?
Thanks,
David
> Author: Anders Lindgren <andlind@gmail.com>
> Date: Tue Mar 22 20:18:33 2016 +0100
>
> Make `toggle-frame-maximized' respect the dock on OS X (bug#22988).
>
> * src/nsterm.m (ns_screen_margins): New function.
> (ns_screen_margins_ignoring_hidden_dock): New function.
> (ns_menu_bar_height): Reimplement in terms of `ns_screen_margins'.
> ([EmacsWindow zoom:]): Take all screen margins (except those
> originating from a hidden dock) into account.
>
next reply other threads:[~2016-03-25 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 2:59 David Reitter [this message]
2016-03-25 7:05 ` recent change to nsterm.m: four pixels where the Dock is hidden Anders Lindgren
2016-03-25 10:56 ` David Reitter
2016-03-25 21:13 ` Anders Lindgren
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=25AFEF78-9B39-41F1-BC01-0208500E2711@gmail.com \
--to=david.reitter@gmail.com \
--cc=andlind@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 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.