unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: 19482@debbugs.gnu.org
Subject: bug#19482: Changing to big font cause display problem
Date: Wed, 25 Feb 2015 08:34:39 +0100	[thread overview]
Message-ID: <54ED7B0F.2070101@gmx.at> (raw)
In-Reply-To: <7F209FD7-19DD-4F47-A8BF-98E88EC65FCB@swipnet.se>

 > It is a bug, popups will popup at the wrong position.  We need to track all four sides.
 > I'm implementing that.

Thanks.

 > But I still think you are confused about what is outer and inner
 > window here.

For the purpose of `x-frame-geometry' the outer window of a frame on X
is the one returned by FRAME_OUTER_WINDOW.  The inner window is the one
whose size is given by FRAME_PIXEL_WIDTH and FRAME_PIXEL_HEIGHT.
`x-frame-geometry' should return in 'frame-outer-size' the size of the
_outer window_ including any external toolbar or menubar "attached to
that window" (I'm not interested in "floating" bars).  This way, Emacs
can check whether the outer window fits conceptually into the working
area of its display.

 > In the macro OUTER_TO_INNER_DIFF outer refers to the
 > window that the windowmanager puts as Emacs parent.  "Inner" here is
 > actually the outermost Emacs created X window, and "outer" is the
 > window manager window.  So outer contains the title bar,

IIUC the only problem is whether the "window manager window" does
contain the external toolbar/mmenubar.  The title bar and the external
borders are definitely part of the window manager window.

 > but this:
 >
 >    outer_width = FRAME_PIXEL_WIDTH (f) + 2 * border;
 >    outer_height = (FRAME_PIXEL_HEIGHT (f)
 > 		  + FRAME_OUTER_TO_INNER_DIFF_Y (f)
 > 		  + FRAME_OUTER_TO_INNER_DIFF_X (f));
 >
 >
 > is just plain wrong, because for you are calculating something that
 > does not correspond to any real window.  For example, on Gnome 3 the
 > window manager puts in a window that is 10 pixels wider on both sides,
 > so it can do shadow effects.  But the border is still one or zero
 > pixels.

FRAME_OUTER_TO_INNER_DIFF_Y gives me only the offset of the top left
corner, that is, the difference of the top edge of the outer window and
the inner window.  I don't know how to get the difference between the
bottom edge of the Emacs window and the bottom edge of the outer window.
So I approximate.  This approximation obviously goes wrong when the left
and bottom borders are not the same size.  Can you tell me a better way?

 > So what you have calculated is not the window manager window sizes,
 > because inner_to_outer width is not taken into account.

FRAME_OUTER_TO_INNER_DIFF_X gives me the offset of the left edge of the
inner window wrt the outer window.  The only thing I can do is multiply
it by two.  As mentioned earlier, if these differences are not
symmetric, for example, because one border is larger than the other, the
information provided is wrong.  Again, it's the best approximation I can
come up with so far.

 > There
 > actually is no window with width FRAME_PIXEL_WIDTH + 2 * border in the
 > Gnome 3 case.

Are you sure?  Does FRAME_OUTER_TO_INNER_DIFF_X not include the extra 10
pixels you mentioned above?

 > For Gtk+/Motif/Lucid, we create a window outside the
 > frame (i.e. text editing part) that contains the tool bar if external,
 > menu bar and scroll bar.  But that window is not this size either, the
 > width would in general contain the scroll bar for example.

That would be devastating.  Scroll bars are part of the inner window.

 > So what are you trying to calculate?  Is it the window manager window
 > geometry, or the geometry of the largest Emacs created window?

The sizes of the outer window aka window manager window.  The size of
the largest Emacs created window is returned by `x-frame-geometry' for
comparison purpose only (via 'frame-inner-size').

martin





  reply	other threads:[~2015-02-25  7:34 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01 15:21 bug#19482: Changing to big font cause display problem 张海君
2015-02-13 18:28 ` martin rudalics
2015-02-18 11:19   ` 张海君
2015-02-18 14:05     ` martin rudalics
2015-02-19  1:59       ` 张海君
2015-02-19  6:57         ` martin rudalics
2015-02-20 10:23           ` 张海君
2015-02-20 18:21             ` martin rudalics
2015-02-21  1:33               ` 张海君
2015-02-21 11:44                 ` martin rudalics
2015-02-22  2:57                   ` 张海君
2015-02-22 10:00                     ` martin rudalics
2015-02-22 10:54                       ` 张海君
2015-02-22 11:32                         ` martin rudalics
2015-02-22 12:27                           ` 张海君
2015-02-22 17:09                             ` martin rudalics
2015-02-23  2:11                               ` 张海君
2015-02-22 16:27                         ` Jan D.
2015-02-22 17:10                           ` martin rudalics
2015-02-22 17:43                             ` Jan D.
2015-02-22 18:52                               ` martin rudalics
2015-02-23  6:22                                 ` Jan D.
2015-02-24 19:09                                   ` Jan D.
2015-02-25  7:34                                     ` martin rudalics [this message]
2015-02-25  9:20                                       ` Jan D.
2015-02-25 10:33                                         ` martin rudalics
2015-02-25 15:27                                           ` Jan D.
2015-02-25 17:33                                             ` martin rudalics
2015-02-25 18:25                                               ` Jan D.
2015-02-25 19:00                                                 ` martin rudalics
2015-02-25 20:22                                                   ` Jan D.
2015-02-27  8:30                                                     ` martin rudalics
2015-02-27 17:49                                                       ` Jan D.
2015-02-25 19:17                                                 ` Jan D.
2015-02-27  8:30                                                   ` martin rudalics
2015-02-27 17:52                                                     ` Jan D.
2015-02-27 19:49                                                       ` martin rudalics
2015-02-27 20:29                                                         ` Jan D.
2015-03-01 15:14                                                         ` martin rudalics
2015-03-01 16:18                                                           ` Jan D.
2015-03-10 14:36                                     ` 张海君
2015-03-10 18:47                                       ` martin rudalics
2015-03-12  5:14                                         ` Jan D.
2015-03-12 10:13                                           ` martin rudalics
2015-03-12 16:52                                             ` Eli Zaretskii
2015-03-12 18:21                                             ` Jan D.

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=54ED7B0F.2070101@gmx.at \
    --to=rudalics@gmx.at \
    --cc=19482@debbugs.gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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).