From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: esabof@gmail.com, 14233@debbugs.gnu.org
Subject: bug#14233: 24.3; Don't constrain frame size to character multiples
Date: Wed, 24 Apr 2013 08:39:39 +0200 [thread overview]
Message-ID: <51777E2B.6090508@gmx.at> (raw)
In-Reply-To: <83zjwpw5uh.fsf@gnu.org>
>> > We do have macros like FRAME_MENUBAR_HEIGHT and FRAME_TOOLBAR_HEIGHT
>> > that can be used. It is better to have that calculation in one place,
>> > rather than in each port, so this might be a good time to move it.
>>
>> If someone wants and knows how to do this cleanly, please go for it.
>
> Can you explain what macros/functions would you like to have, exactly,
> to be able to do this job cleanly? Maybe FRAME_MENUBAR_HEIGHT
> etc. are not what you need, but perhaps there are other means to get
> the information cleanly.
A function that would tell me in a platform independent way the pixel
offset of the frame's root window from the top edge of the frame's
"client rectangle" (sorry for the Windows parlance).
I can calculate the remaining pixel edges of the frame's root window by
subtracting the frame's interior pixel width around it. The minibuffer
window has either what frame-char-height tells me or gets me its pixel
height exactly when called by resize_mini_window. So the upper part is
the only missing one (modulo the fringe/scrollbar tribulations mentioned
elsewhere).
martin
next prev parent reply other threads:[~2013-04-24 6:39 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 23:58 bug#14233: 24.3; Don't constrain frame size to character multiples E Sabof
2013-04-20 0:17 ` Glenn Morris
2013-04-20 6:45 ` Eli Zaretskii
2013-04-20 8:53 ` martin rudalics
2013-04-20 9:11 ` Jan Djärv
2013-04-20 11:00 ` martin rudalics
2013-04-20 12:56 ` Jan Djärv
2013-04-20 13:13 ` Eli Zaretskii
2013-04-20 19:26 ` Jan Djärv
2013-04-20 19:54 ` Eli Zaretskii
2013-04-20 22:02 ` Drew Adams
2013-04-21 3:40 ` Stefan Monnier
2013-04-21 7:04 ` Jan Djärv
2013-04-21 9:28 ` martin rudalics
2013-04-21 17:05 ` Jan Djärv
2013-04-22 9:34 ` martin rudalics
2013-04-22 14:17 ` Stefan Monnier
2013-04-21 9:27 ` martin rudalics
2013-04-21 9:27 ` martin rudalics
2013-04-20 20:47 ` E Sabof
2013-04-21 9:26 ` martin rudalics
2013-04-21 17:21 ` Jan Djärv
2013-04-22 9:34 ` martin rudalics
2013-04-22 13:11 ` Jan Djärv
2013-04-22 15:36 ` martin rudalics
2013-04-22 16:11 ` Jan Djärv
2013-04-22 16:38 ` martin rudalics
2013-04-22 18:21 ` Eli Zaretskii
2013-04-23 6:52 ` martin rudalics
2013-04-23 16:28 ` Eli Zaretskii
2013-04-24 6:39 ` martin rudalics
2013-04-24 17:13 ` Eli Zaretskii
2013-04-23 11:58 ` Jan Djärv
2013-04-23 12:33 ` martin rudalics
2013-04-23 16:48 ` Eli Zaretskii
2013-04-24 6:39 ` martin rudalics [this message]
2013-04-24 16:54 ` Jan Djärv
2013-04-25 7:29 ` martin rudalics
2013-04-25 9:55 ` Jan Djärv
2013-04-25 11:58 ` martin rudalics
2013-04-25 15:47 ` Richard Stallman
2013-04-24 17:15 ` Eli Zaretskii
2013-04-24 17:50 ` Jan Djärv
2013-04-25 7:29 ` martin rudalics
2013-04-20 13:38 ` martin rudalics
2013-04-20 19:33 ` Jan Djärv
2013-04-20 16:22 ` Drew Adams
2013-04-20 17:12 ` Eli Zaretskii
2013-04-20 21:50 ` Drew Adams
2013-04-21 9:27 ` martin rudalics
2013-04-21 16:17 ` Drew Adams
2013-04-20 9:25 ` Eli Zaretskii
2013-04-20 11:01 ` martin rudalics
2013-04-20 11:32 ` Eli Zaretskii
2013-04-20 13:38 ` martin rudalics
2013-04-20 16:25 ` Eli Zaretskii
2013-04-20 17:35 ` martin rudalics
2013-04-20 17:48 ` E Sabof
2013-04-20 18:26 ` Eli Zaretskii
2013-04-21 9:26 ` martin rudalics
2013-04-21 15:03 ` Eli Zaretskii
2013-04-22 9:34 ` martin rudalics
2013-04-21 17:30 ` Jan Djärv
2013-04-22 9:34 ` martin rudalics
2013-04-22 13:12 ` Jan Djärv
2013-04-22 15:36 ` martin rudalics
2013-04-22 18:36 ` Eli Zaretskii
2013-04-23 6:54 ` martin rudalics
2013-04-23 16:29 ` Eli Zaretskii
2013-04-23 6:50 ` martin rudalics
2013-04-23 16:23 ` Eli Zaretskii
2013-04-24 6:38 ` martin rudalics
2013-04-24 17:09 ` Eli Zaretskii
2013-04-24 18:50 ` Stefan Monnier
2013-04-24 20:09 ` Jan Djärv
2013-04-25 7:31 ` martin rudalics
2013-04-25 10:02 ` Jan Djärv
2013-04-25 11:58 ` martin rudalics
2013-04-25 14:11 ` Jan Djärv
2013-04-25 7:30 ` martin rudalics
2013-04-25 7:29 ` martin rudalics
2013-04-25 16:24 ` Eli Zaretskii
2013-04-26 7:42 ` martin rudalics
2013-04-26 13:21 ` Stefan Monnier
2013-04-26 14:39 ` Drew Adams
2013-04-27 6:59 ` martin rudalics
2013-04-27 13:53 ` Drew Adams
2013-04-28 12:17 ` martin rudalics
2013-04-28 15:33 ` Drew Adams
2013-04-28 16:29 ` Drew Adams
2013-04-29 7:33 ` martin rudalics
2013-04-29 14:10 ` Drew Adams
2013-04-29 16:48 ` martin rudalics
2013-04-29 20:41 ` Drew Adams
2013-04-30 7:34 ` martin rudalics
2013-04-30 15:47 ` Drew Adams
2013-04-30 17:08 ` martin rudalics
2013-04-30 19:45 ` Drew Adams
2013-05-01 9:15 ` martin rudalics
2013-05-01 13:47 ` Drew Adams
2013-05-02 9:22 ` martin rudalics
2013-05-02 13:28 ` Drew Adams
2014-12-25 19:30 ` martin rudalics
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=51777E2B.6090508@gmx.at \
--to=rudalics@gmx.at \
--cc=14233@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=esabof@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).