From: David Kastrup <dak@gnu.org>
Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org,
stahl@eos.franken.de, Eli Zaretskii <eliz@gnu.org>,
snogglethorpe@gmail.com, miles@gnu.org
Subject: Re: Tooltips on w32 slow and strange
Date: Tue, 15 Feb 2005 01:27:15 +0100 [thread overview]
Message-ID: <x5fyzyu0po.fsf@lola.goethe.zz> (raw)
In-Reply-To: <uzmy6k82o.fsf@jasonrumney.net> (Jason Rumney's message of "Mon, 14 Feb 2005 23:58:23 +0000")
Jason Rumney <jasonr@gnu.org> writes:
> Miles Bader <snogglethorpe@gmail.com> writes:
>
>> On Mon, 14 Feb 2005 22:28:19 +0200, Eli Zaretskii <eliz@gnu.org> wrote:
>>> > "Emacs Frame" tooltips seems to work really well in X11; why not just
>>> > make them work well in Windows too?
>>>
>>> FWIW, I use Emacs on Windows XP and never saw any special slowness
>>> of the Emacs tooltips.
>>
>> Might it be simply that Windows is very slow in window-creation (it
>> is reputedly much slower to create new OS processes than other
>> OSes) and the original poster has a very slow machine?
>
> I think any slowness to create windows would not be perceptable, as
> it would just mean a slightly longer delay before the tooltip pops
> up. The perceived slowness I think is the delay between window
> creation and drawing its contents. We might be able to hide the
> tooltip window until it is completely drawn so the user does not see
> this.
Uh, disagree. The really disturbing effect of a tooltip popup is when
you type keys and Emacs basically appears to freeze without
explanation until the Windows pops up. Once we start working on a
tooltip, response is gone until we finished the tooltip. So it is
essential that we do the tooltip in the fastest possible way. Double
buffering not only makes the operation slower, it also removes the
possibility of guessing just why the machine does not react
immediately.
> But the other problem of focus changing when tooltips pop up is more
> urgent, I think.
That too...
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-02-15 0:27 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 [this message]
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
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=x5fyzyu0po.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
--cc=miles@gnu.org \
--cc=snogglethorpe@gmail.com \
--cc=stahl@eos.franken.de \
/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).