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 21:34:27 +0100 [thread overview]
Message-ID: <87mvrdzigc.fsf@wanadoo.es> (raw)
In-Reply-To: <56B64E2E.5040006@gmx.at> (martin rudalics's message of "Sat, 06 Feb 2016 20:49:02 +0100")
martin rudalics <rudalics@gmx.at> writes:
>> I suppose you tested with underlying text very near the dividing screen
>> edge. When you drag the frame with the mouse from left to right and
>> back does the tooltip "jump" accordingly from one monitor to the other?
>
> No that's silly because the mouse must be on the frame border for
> dragging. So you have to release the mouse first and move it to the
> appropriate text.
Furthermore, the tooltip frame isn't supposed to move once it is
displayed, AFAIK.
I'll commit the patch soon, but the bug will remain open until I check
the MS Windows case. The test on Windows I mentioned at the beginning of
this issue was not valid, because it used only monitor. It is frequent
to connect MS Windows laptops to an external monitor and use both
displays, effectively duplicating the setup I have on GNU/Linux: two
monitors with different resolutions.
next prev parent reply other threads:[~2016-02-06 20:34 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
2016-02-06 19:44 ` martin rudalics
2016-02-06 19:49 ` martin rudalics
2016-02-06 20:34 ` Óscar Fuentes [this message]
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
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=87mvrdzigc.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 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).