From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Coordinates and Windows
Date: Fri, 17 Jul 2015 16:09:43 +0300 [thread overview]
Message-ID: <83y4if53s8.fsf@gnu.org> (raw)
In-Reply-To: <55A7F68A.3040003@gmx.at>
> Date: Thu, 16 Jul 2015 20:23:06 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: emacs-devel@gnu.org
>
> > I don't see why. Having the top-left corner of the frame as the
> > reference point sounds simpler and more clear to me, and allows one to
> > use it in the same way in all the builds. No?
>
> If by top-left corner you intend the top-left position of the menu bar,
> or if that's absent that of the top/left tool bar, or if that's absent
> too that of the internal border, or if that is absent too that of the
> root window
Yes.
> I agree. Just that it's not all too trivial to calculate it.
In pixels or in rows?
> >> To illustrate how little care has been applied to this so far, consider
> >> the function `window-absolute-pixel-edges'. With a maximized frame on
> >> Windows XP this function returns (-4 -4 1676 964) here.
> >
> > I get (-8 28 1912 984) on Windows 7 and (-4 32 1916 1022) on XP, so at
> > least the Y coordinate seems OK.
>
> Just 32 pixels for title, menu, and tool bar?
Maybe I'm confused, but doesn't that include only the title and menu
on Windows? Or maybe just the title?
> BTW, has Windows 7 an 8 pixel wide border by default?
How can I know?
> No, off-screen decorations are a Windows feature. What I meant is that
> Gtk has some established, working features that albeit never worked on
> Windows. And I'm afraid to break these features.
Isn't that what development is about -- breaking features and then
fixing the breakage?
next prev parent reply other threads:[~2015-07-17 13:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 7:00 Coordinates and Windows martin rudalics
2015-07-15 14:57 ` Eli Zaretskii
2015-07-15 18:21 ` martin rudalics
2015-07-15 19:34 ` Eli Zaretskii
2015-07-16 7:14 ` martin rudalics
2015-07-16 14:32 ` Eli Zaretskii
2015-07-16 18:23 ` martin rudalics
2015-07-17 13:09 ` Eli Zaretskii [this message]
2015-07-17 13:36 ` martin rudalics
2015-07-17 14:21 ` Eli Zaretskii
2015-07-17 17:58 ` martin rudalics
2015-07-17 18:10 ` Eli Zaretskii
2015-07-18 9:03 ` martin rudalics
[not found] ` <<83wpxy6f0x.fsf@gnu.org>
2015-07-17 15:09 ` Drew Adams
2015-07-17 17:58 ` martin rudalics
2015-07-17 19:28 ` Drew Adams
2015-07-18 9:03 ` martin rudalics
2015-07-19 16:47 ` Eli Zaretskii
2015-07-20 6:42 ` martin rudalics
2015-07-20 7:04 ` martin rudalics
2015-07-20 16:15 ` Eli Zaretskii
[not found] <<55A60508.7090903@gmx.at>
[not found] <"<83oajd79kz.fsf"@gnu.org>
[not found] ` <"<83fv4p6wqp.fsf"@gnu.org>
[not found] ` <"<83bnfc6um1.fsf"@gnu.org>
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=83y4if53s8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).