From: Stephen Berman <stephen.berman@gmx.net>
To: Jason Rumney <jasonr@gnu.org>
Cc: 2360@emacsbugs.donarmstrong.com
Subject: bug#2360: 23.0.90; redirect-frame-focus induces translucent tooltips/frames
Date: Thu, 19 Feb 2009 17:32:40 +0100 [thread overview]
Message-ID: <87prhel74n.fsf@escher.local.home> (raw)
In-Reply-To: <499D7582.1080004@gnu.org> (Jason Rumney's message of "Thu, 19 Feb 2009 23:06:42 +0800")
On Thu, 19 Feb 2009 23:06:42 +0800 Jason Rumney <jasonr@gnu.org> wrote:
> Stephen Berman wrote:
>> 3. M-: (redirect-frame-focus (selected-frame) (previous-frame))
>> a. Move mouse cursor over a tool bar icon and observe that the
>> tooltip is translucent and very light, barely visible.
>> b. Type `C-x 5 2' and observe that the newly created frame is
>> likewise translucent and barely visible.
>>
>
>
> I can confirm that 3a is reproducible on Windows too (even without steps 1 and
> 2), but I do not see 3b (but that seemed to depend on font, font-size and
> font-backend in your tests, so maybe there is a different combination that can
> reproduce 3b on Windows).
>
> I would guess this was introduced when the transparency patch went in or some
> time after, rather than by the unicode merge.
This seems likely; indeed, when I start Emacs like this:
$ emacs -Q --eval "(setq default-frame-alist '((alpha . 30)))"
and then type `C-x 5 2', the newly created frame has about the same
appearance as what I see after calling redirect-frame-focus.
(Interestingly, and something I failed to notice in my OP, the tooltips
generated from the transparent frame are not transparent; i.e., in the
case of my OP, only the tooltips of the first frame are transparent).
Steve Berman
next prev parent reply other threads:[~2009-02-19 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 15:54 bug#2360: 23.0.90; redirect-frame-focus induces translucent tooltips/frames Stephen Berman
2009-02-19 15:06 ` Jason Rumney
2009-02-19 16:32 ` Stephen Berman [this message]
2021-07-19 14:54 ` Lars Ingebrigtsen
2021-07-19 16:05 ` Stephen Berman
2021-07-19 16:24 ` Lars Ingebrigtsen
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=87prhel74n.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--cc=2360@emacsbugs.donarmstrong.com \
--cc=jasonr@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 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).