unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: [Chong Yidong] Re: Tool-bar buttons unresponsive with tooltips on
Date: Mon, 17 Oct 2005 21:12:08 -0400	[thread overview]
Message-ID: <87psq3ljbr.fsf@stupidchicken.com> (raw)
In-Reply-To: <4353A92A.2040004@gnu.org> (Jason Rumney's message of "Mon, 17 Oct 2005 14:37:46 +0100")

>     It seems to be related to a setting in KDE's window manager, "Click
> Raise Active Window".
>
> Interesting (but I still don't understand where the problem is, or
> what triggers it).
>   
>
> What happens to last_mouse_glyph when you click on the toolbar? In a
> GTK build (where the toolbar is a GTK widget) and in a non-GTK build
> (where the toolbar is part of the Emacs frame's client area).
>
> Do we still have a bug in the (virtual) glyph used for mouse tracking
> in one of these cases?

I think Emacs doesn't register the click at all.  When I do `C-h k',
and click on the toolbar button (after waiting for the tooltip to pop
up), nothing happens.  I think the window manager is eating the click
event.  Since Emacs tooltips are actual frames (X windows), my guess
is that the window manager is trying to "raise" the tooltip.

Why the recent changes would unearth this problem, I am still trying
to find out.

  reply	other threads:[~2005-10-18  1:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-16 22:59 [Chong Yidong] Re: Tool-bar buttons unresponsive with tooltips on Kim F. Storm
2005-10-17  7:36 ` Jason Rumney
2005-10-17  8:42   ` Kim F. Storm
2005-10-17 13:19     ` Chong Yidong
2005-10-17 13:28       ` Kim F. Storm
2005-10-17 13:37         ` Jason Rumney
2005-10-18  1:12           ` Chong Yidong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-17 14:19 David PONCE
2005-10-17 16:43 Chong Yidong
2005-10-19  8:39 David PONCE
2005-10-19 17:31 ` Jan D.
2005-10-19 17:57   ` Jan D.

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=87psq3ljbr.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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).