From: "Óscar Fuentes" <ofv@wanadoo.es>
To: martin rudalics <rudalics@gmx.at>
Cc: 22549@debbugs.gnu.org
Subject: bug#22549: 25.0.50; Tooltips placed outside of screen limits
Date: Sat, 06 Feb 2016 19:52:50 +0100 [thread overview]
Message-ID: <87r3gpzn5p.fsf@wanadoo.es> (raw)
In-Reply-To: <56B636CF.2020609@gmx.at> (martin rudalics's message of "Sat, 06 Feb 2016 19:09:19 +0100")
martin rudalics <rudalics@gmx.at> writes:
> But ‘x_display_pixel_height’ returns the value of 'HeightOfScreen' which
> is what we need for the one monitor case.
Ok.
> My concern was less that ‘x-display-monitor-attributes-list’ would not
> assign a value to max_y. My concern was that that value could be wrong.
>
> Anyway. Better install your initial patch then. It's cleaner and we'll
> see soon enough whether it causes any problems.
My initial patch is not better because it doesn't protect against the
possible lack of information on x-display-monitor-attributes-list you
mentioned above and on your previous e-mail. If that structure has not
the correct geometry info about the current monitor, the variables
max/min_x/y are guaranteed to be wrong. My last patch provides some
protection against that circunstance, so I'll feel better committing it.
(BTW, the path is basically yours, not mine. I just corrected some
issues but the 90% was written by you, so I'll feel a bit uneasy taking
credit for it.)
>>> And just to make sure: Can we rely on the fact that XQueryPointer always
>>> gives reliable results with multiple monitors and its present arguments?
>>
>> Dunno. I know nothing about X Windows.
>
> Have you tried with a frame that spans both monitors?
Just tried. It seems to work fine: for a frame that spawns both
monitors, the tooltip is correctly positioned taking into account the
coordinates of the mouse cursor and the geometry of the corresponding
monitor.
next prev parent reply other threads:[~2016-02-06 18:52 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
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 [this message]
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=87r3gpzn5p.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=22549@debbugs.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 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.