From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 22549@debbugs.gnu.org
Subject: bug#22549: 25.0.50; Tooltips placed outside of screen limits
Date: Thu, 04 Feb 2016 18:43:21 +0200 [thread overview]
Message-ID: <83vb64whna.fsf@gnu.org> (raw)
In-Reply-To: <87r3gs30rk.fsf@wanadoo.es> (message from Óscar Fuentes on Thu, 04 Feb 2016 17:20:47 +0100)
> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Thu, 04 Feb 2016 17:20:47 +0100
> Cc: 22549@debbugs.gnu.org
>
> >> The MS Windows port places the tooltips taking into account the screen
> >> edges.
> >
> > So does the Lucid port. Something else must be at work here.
>
> I think I know what is happening.
>
> I have two monitors, side by side, simulating a continuous display. The
> monitor on the left side, where Emacs is displayed, has a vertical
> resolution of 1050 pixels while the monitor on the right side has a
> vertical resolution of 1200 points. Emacs is using the vertical
> resolution of the virtual display (the largest of the two monitors, i.e.
> 1200 points) instead of the resolution of the monitor that hosts the
> Emacs frame.
>
> Something similar happens for the horizontal overflow: the dimensions of
> the virtual desktop are used instead of the dimensions of the monitor.
I arrived at the same conclusion by looking at the X code: the APIs
called by x_display_pixel_height and x_display_pixel_width return
information about the entire virtual screen, not about the current
monitor. We need to use different APIs in the case of tooltip
positioning.
next prev parent reply other threads:[~2016-02-04 16:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 4:05 bug#22549: 25.0.50; Tooltips placed outside of screen limits Óscar Fuentes
2016-02-04 15:55 ` martin rudalics
2016-02-04 16:20 ` Óscar Fuentes
2016-02-04 16:43 ` Eli Zaretskii [this message]
2016-02-04 17:05 ` martin rudalics
2016-02-04 19:16 ` Óscar Fuentes
2016-02-05 17:44 ` martin rudalics
2016-02-05 22:34 ` Óscar Fuentes
2016-02-06 9:30 ` martin rudalics
2016-02-05 23:52 ` Óscar Fuentes
2016-02-06 9:30 ` martin rudalics
2016-02-06 17:06 ` Óscar Fuentes
2016-02-06 18:09 ` martin rudalics
2016-02-06 18:52 ` Óscar Fuentes
2016-02-06 19:44 ` martin rudalics
2016-02-06 19:49 ` martin rudalics
2016-02-06 20:34 ` Óscar Fuentes
2016-02-06 21:23 ` Óscar Fuentes
2016-02-06 22:56 ` martin rudalics
2016-02-06 23:22 ` Óscar Fuentes
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=83vb64whna.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22549@debbugs.gnu.org \
--cc=ofv@wanadoo.es \
/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.