From: Drew Adams <drew.adams@oracle.com>
To: 17344@debbugs.gnu.org
Subject: bug#17344: 24.3.90; REGRESSION: tooltip semi-transparent in *Completions*
Date: Mon, 28 Apr 2014 11:10:38 -0700 (PDT) [thread overview]
Message-ID: <cabb7007-30f3-4b56-9cbe-494db5001b03@default> (raw)
In-Reply-To: <5768bb5c-7e46-4017-9d6c-018b51f5dd4b@default>
Some more info about this regression:
(I cannot get a screen capture to show you, because my screen-capture
tool does not capture tooltips.)
If I give another, non-Emacs window-manager window the focus (by clicking
its title bar) then the mouseover tooltip in the *Completions* frame is OK
(normal, not transparent).
And, as I think I said earlier, if I give the minibuffer frame the focus,
same thing: the tooltip is normal, not transparent. But if I give any other
Emacs frame the focus (including frame *Completions*), e.g., by clicking its
title bar, then the tooltip in *Completions* is transparent.
Note that typically some other frame has the input focus when the minibuffer
is activated, and it keeps the focus during use of the minibuffer.
I'm not real clear on the terminology, however. Suppose I click the title
bar of a Dired frame or a frame for *Messages*. Then if I do, say, `M-x',
the minibuffer becomes active and it accepts input. But it its title bar
is not colored to show that it has the focus - the Dired or whatever frame
that had the focus still has it, as judged by its title bar.
So what kind of focus is this, since typing input puts it in the minibuffer?
The minibuffer frame does not have the "focus", but input goes to it. (And
a call to `select-frame-set-input-focus' for the minibuffer frame does
change its title bar, "focusing" it, and even after the minibuffer is exited
the minibuffer frame then still has that focus.)
next prev parent reply other threads:[~2014-04-28 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 4:43 bug#17344: 24.3.90; REGRESSION: tooltip semi-transparent in *Completions* Drew Adams
2014-04-28 18:10 ` Drew Adams [this message]
2015-07-04 8:47 ` martin rudalics
2015-07-04 14:52 ` 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=cabb7007-30f3-4b56-9cbe-494db5001b03@default \
--to=drew.adams@oracle.com \
--cc=17344@debbugs.gnu.org \
/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.