From: "Stephan Stahl" <stahl@eos.franken.de>
Cc: stahl@eos.franken.de, snogglethorpe@gmail.com,
emacs-devel@gnu.org, miles@gnu.org
Subject: Re: Tooltips on w32 slow and strange
Date: Tue, 15 Feb 2005 09:53:40 +0100 (CET) [thread overview]
Message-ID: <34459.217.194.34.123.1108457620.squirrel@wwws.franken.de> (raw)
In-Reply-To: <01c51319$Blat.v2.4$54fb6980@zahav.net.il>
Hi.
Eli Zaretskii said:
> I don't know. How about if the OP tells us how much time it takes for
> the tooltip to pop up, and what machine is that?
I'm not the OP but using Miles Example and C-x C-e'ing it seems fast
enough and takes about half a second on an P4 2,4GHz running XP.
(x-show-tip
(propertize "*** hello ***"
'face '(variable-pitch :foreground "green"
:background "steelblue"
:height 3.0)))
I'd like to provide some findings regarding the strange focus
handling:
emacs -q --no-site-init
C-x 2
C-x b bla (make it easy to recognise the two frames)
put the mouse on the toolbar to create a popup works fine.
Alt-Tab (using XP to switch frames)
put the mouse on the toolbar to create a popup will NOT work right.
(i do not even see the popup but the first frame with
the *scratch* buffer pops up while the second with the
bla buffer still has input focus.
Maybe it is the second frame with the bla buffer that
pops-under??? if this is possible..)
Now try doing the same thing but using C-x 5 o to switch the frames will
cause the popup to work just fine. Does C-x 5 o some thing special
compared to Alt-tab?
Maybe this will help someone..
Stephan
--
Stephan Stahl
next prev parent reply other threads:[~2005-02-15 8:53 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 0:21 Tooltips on w32 slow and strange Lennart Borgman
2005-02-13 18:21 ` Stefan Daschek
2005-02-14 8:15 ` Stephan Stahl
2005-02-14 9:58 ` Jason Rumney
2005-02-14 10:13 ` Stephan Stahl
2005-02-14 10:27 ` Jason Rumney
2005-02-14 12:26 ` David Kastrup
2005-02-14 13:07 ` Jason Rumney
2005-02-14 14:41 ` Lennart Borgman
2005-02-14 15:19 ` Jason Rumney
2005-02-14 18:02 ` Lennart Borgman
2005-02-14 15:02 ` Miles Bader
2005-02-14 15:47 ` David Kastrup
2005-02-14 15:57 ` Ralf Angeli
2005-02-14 17:16 ` David Kastrup
2005-02-14 17:29 ` Jason Rumney
2005-02-14 17:39 ` Reiner Steib
2005-02-14 18:29 ` Stefan Monnier
2005-02-14 17:56 ` Ralf Angeli
2005-02-14 18:55 ` Jan D.
2005-02-14 19:44 ` Ralf Angeli
2005-02-14 19:59 ` Jan D.
2005-02-14 20:14 ` David Kastrup
2005-02-15 8:15 ` Ralf Angeli
2005-02-16 1:02 ` Oliver Scholz
2005-02-14 18:42 ` Jan D.
2005-02-14 18:50 ` David Kastrup
2005-02-14 19:02 ` Jan D.
2005-02-14 13:54 ` Lennart Borgman
2005-02-14 15:08 ` Miles Bader
2005-02-14 20:28 ` Eli Zaretskii
2005-02-14 23:48 ` Miles Bader
2005-02-14 23:58 ` Jason Rumney
2005-02-15 0:27 ` David Kastrup
2005-02-15 0:01 ` Lennart Borgman
2005-02-15 0:47 ` Kenichi Handa
2005-02-15 6:19 ` Jan D.
2005-02-15 16:29 ` Stefan Monnier
2005-02-15 4:45 ` Eli Zaretskii
2005-02-15 8:53 ` Stephan Stahl [this message]
2005-02-15 10:02 ` Jason Rumney
2005-02-15 10:11 ` Stephan Stahl
2005-02-15 10:31 ` Jason Rumney
2005-02-15 13:43 ` Lennart Borgman
2005-02-15 14:19 ` Jason Rumney
2005-02-15 15:31 ` Lennart Borgman
2005-02-15 20:03 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2005-03-08 9:07 Stephan Stahl
2005-03-08 10:40 ` Stephan Stahl
2005-03-08 12:43 ` Jason Rumney
2005-03-08 15:42 ` Lennart Borgman
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=34459.217.194.34.123.1108457620.squirrel@wwws.franken.de \
--to=stahl@eos.franken.de \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=snogglethorpe@gmail.com \
/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).