unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: Glitches with the GTK toolkit
Date: Fri, 07 Jan 2005 18:32:54 +0100	[thread overview]
Message-ID: <41DEC7C6.70601@swipnet.se> (raw)
In-Reply-To: <wlekh05ck4.wl%mituharu@math.s.chiba-u.ac.jp>

YAMAMOTO Mitsuharu wrote:

>This topic is somewhat old.  But I'd like to take up this because the
>similar problem also occurs in Carbon Emacs, where drawing text is
>much slower than in X11.
>

In the GTK case, it was the drawing of scroll bars that was slow.  But 
it is a lot faster now, it should be equally fast as for other GTK 
applications.

>How about preventing redisplay from pausing in the case that there are
>no pending inputs other than the mouse movement?  One can "squeeze" a
>sequence of mouse movement events into the latest one, and I think
>it's OK to postpone such kind of events until redisplay is completed.
>
>Here's a patch for testing the above idea.  It would be better to make
>redisplay pause even in the case mentioned above, if the latest mouse
>movement gets too old.
>

On GTK I actually don't see any difference, but on OSX I do.  It is an 
improvement, and slower machines will probably benefit.  Does this 
affect any other operations that dragging the mode line?

    Jan D.

  reply	other threads:[~2005-01-07 17:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-10 13:51 Glitches with the GTK toolkit Jérôme Marant
2004-05-11  1:24 ` Miles Bader
2004-05-11  8:03   ` Jérôme Marant
2004-05-11  8:45     ` Miles Bader
2004-05-11  6:56       ` Kim F. Storm
2004-05-11 18:33         ` Jérôme Marant
2004-05-11 18:30       ` Jérôme Marant
2004-05-11 19:17         ` Jan D.
2004-05-11 20:44           ` Jérôme Marant
2004-05-11 21:18             ` Jan D.
2004-05-11 21:34               ` Jérôme Marant
2004-05-11 21:53                 ` Jan D.
2004-05-12 11:37                   ` Jérôme Marant
2004-05-12 11:58                     ` Jan D.
2004-05-12 21:03                       ` Jérôme Marant
2005-01-05 11:40                 ` YAMAMOTO Mitsuharu
2005-01-07 17:32                   ` Jan D. [this message]
2005-01-08  9:11                     ` YAMAMOTO Mitsuharu
2005-01-08  9:49                       ` Jan D.
2004-05-12  1:33             ` Miles Bader
2004-05-12 11:34               ` Jérôme Marant
2004-05-12 18:33                 ` Kim F. Storm
2004-05-12 21:07                   ` Jérôme Marant
2004-05-12 22:32                     ` Miles Bader
2004-05-13 11:55                       ` Jérôme Marant
2004-05-13 19:30                         ` Miles Bader
2004-05-13  5:46                     ` Eli Zaretskii
2004-05-13 11:57                       ` Jérôme Marant
2004-05-13 13:51                         ` Kim F. Storm
2004-05-14  7:21                           ` Jérôme Marant

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=41DEC7C6.70601@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@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).