unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Coordinates and Windows
Date: Fri, 17 Jul 2015 19:58:12 +0200	[thread overview]
Message-ID: <55A94234.7070600@gmx.at> (raw)
In-Reply-To: <83wpxy6f0x.fsf@gnu.org>

 > Why does it matter if we get that accurately, in builds where we don't
 > manage those decorations?  We might as well approximate that with some
 > reasonable value, and be done, no?

For example, on Windows I need accurate dimensions of decorations to
emulate fullheight and fullwidth fullscreen modes.  And if I want to
display a tooltip at a certain position within a window I need them as
well.

 >> This would imply that the tool bar (and maybe even the menu bar) are
 >> part of the root window.
 >
 > Which on Windows, it is, AFAIK.

No.  The root window is beneath the tool bar window separated from the
latter by the internal border.

 >>   >> BTW, has Windows 7 an 8 pixel wide border by default?
 >>   >
 >>   > How can I know?
 >>
 >> What does M-: (x-frame-geometry) give for you?
 >
 > This is on XP:
 >
 >    ((frame-position -4 . -4) (frame-outer-size 1928 . 1088) (external-border-size 4 . 4) (title-height . 19) (menu-bar-external . t) (menu-bar-size 1920 . 19) (tool-bar-external) (tool-bar-position . top) (tool-bar-size 1920 . 36) (frame-inner-size 1920 . 1042))

This doesn't help me to find out why your `window-absolute-pixel-edges'
returns (-8 28 1912 984) on Windows 7.  I need your value for Windows 7.

martin



  reply	other threads:[~2015-07-17 17:58 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
2015-07-17 13:36               ` martin rudalics
2015-07-17 14:21                 ` Eli Zaretskii
2015-07-17 17:58                   ` martin rudalics [this message]
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=55A94234.7070600@gmx.at \
    --to=rudalics@gmx.at \
    --cc=eliz@gnu.org \
    --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 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).