From: Eli Zaretskii <eliz@gnu.org>
To: Yuuki Harano <masm+emacs@masm11.me>
Cc: 48069@debbugs.gnu.org, email@johnmuhl.mx
Subject: bug#48069: 28.0.50; [feature/pgtk]; tooltips are jittery and sometimes obscured
Date: Tue, 04 May 2021 14:54:20 +0300 [thread overview]
Message-ID: <83czu667f7.fsf@gnu.org> (raw)
In-Reply-To: <20210504.162351.1396008636450564750.masm@luna.pink.masm11.me> (message from Yuuki Harano on Tue, 04 May 2021 16:23:51 +0900 (JST))
> Date: Tue, 04 May 2021 16:23:51 +0900 (JST)
> From: Yuuki Harano <masm+emacs@masm11.me>
> Cc: 48069@debbugs.gnu.org
>
> Tooltips in emacs are written always for main windows, not menu windows,
> and compositor thinks that stacking order should be:
>
> (above)
> - menu
> - tooltip for main window
> - main window
> (below)
>
> It is too hard to improve it...
Does that mean tooltips will not work well in the pgtk build? That
would be a shame, I think. Can we somehow work around this
peculiarity, so that tooltips for menus and tool-bar buttons work as
they do in the other builds?
Thanks.
next prev parent reply other threads:[~2021-05-04 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 17:32 bug#48069: 28.0.50; [feature/pgtk]; tooltips are jittery and sometimes obscured john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-03 16:46 ` Yuuki Harano
2021-05-03 17:16 ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-03 17:47 ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-04 7:23 ` Yuuki Harano
2021-05-04 11:54 ` Eli Zaretskii [this message]
2021-05-04 12:50 ` Yuuki Harano
2021-05-04 13:00 ` Eli Zaretskii
2021-05-08 15:57 ` Yuuki Harano
2021-05-12 15:48 ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-13 15:20 ` Yuuki Harano
2021-05-03 19:33 ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83czu667f7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48069@debbugs.gnu.org \
--cc=email@johnmuhl.mx \
--cc=masm+emacs@masm11.me \
/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).