From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 19925@debbugs.gnu.org
Subject: bug#19925: 25.0.50; mouseover menu items takes up to 30sec to show the proper tooltip or message
Date: Mon, 23 Feb 2015 19:56:31 +0200 [thread overview]
Message-ID: <83y4no7bqo.fsf@gnu.org> (raw)
In-Reply-To: <jwvy4npfdie.fsf-monnier+emacsbugs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Drew Adams <drew.adams@oracle.com>, 19925@debbugs.gnu.org
> Date: Sun, 22 Feb 2015 23:39:52 -0500
>
> Can't we cause regular dummy events?
We could, but sounds complicated, for the same reasons temporarily
binding blink-cursor-blinks to zero is: you'd have to start those
dummy events when the menu is activated (otherwise processing these
events will effectively undo the benign effect of batteries of
stopping the blinking), and stop them when the menu pops down, which
is tricky at best, as I explained elsewhere in this thread.
But if someone wants to work on this, and they come up with a clean
patch, it'd be welcome.
Bonus points for explaining why the tips _are_ displayed, but after a
much longer delays than intended.
next prev parent reply other threads:[~2015-02-23 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 22:54 bug#19925: 25.0.50; mouseover menu items takes up to 30sec to show the proper tooltip or message Drew Adams
2015-02-23 3:42 ` Eli Zaretskii
2015-02-23 4:39 ` Stefan Monnier
2015-02-23 17:56 ` Eli Zaretskii [this message]
2015-02-23 5:17 ` Jan D.
2015-02-23 18:07 ` Eli Zaretskii
[not found] <<1d10f417-acb4-4b32-8bc3-fe949388330d@default>
[not found] ` <<837fv98faf.fsf@gnu.org>
2015-02-23 4:29 ` Drew Adams
2015-02-23 4:33 ` Drew Adams
2015-02-23 17:54 ` Eli Zaretskii
[not found] <<b1bbbbd9-9a78-42e1-bce0-4b2f14666348@default>
[not found] ` <<83zj847bur.fsf@gnu.org>
2015-02-23 19:17 ` Drew Adams
2015-02-23 19:42 ` Eli Zaretskii
[not found] ` <<ffcbfc26-1f09-4b68-ade2-f0e8c16a6115@default>
[not found] ` <<83vbis76tm.fsf@gnu.org>
2015-02-23 19:51 ` Drew Adams
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=83y4no7bqo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19925@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.