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: Emacs GTK scroll-bar flickering
Date: Tue, 18 Mar 2003 06:39:14 +0100	[thread overview]
Message-ID: <F43BC9E3-5903-11D7-A088-00039363E640@swipnet.se> (raw)
In-Reply-To: <buoy93dwjai.fsf@mcspd15.ucom.lsi.nec.co.jp>

>
> I tried today's CVS; it's a bit hard to tell -- maybe the number of
> full-redraws on each buffer change is less, but the overall feel is
> roughly the same (painful).

You must have a very complicated theme or a very slow machine, I can't
see this at all.  Are you sure you updated CVS?

>> There are some of the redraws that can't easily be eliminated.  GDK
>> (the layer under GTK) does its own event buffering, and releases the
>> events when the GTK event loop is entered and there are no events to
>> process.  Since Emacs are not using a pure GTK loop, there might be a
>> very long time before GTK gets a chance to notice this.  So Emacs must
>> force out these events.  Ideally they should not generate any more
>> redraws, just make them happen earlier, but experience shows that we
>> do get redraws.
>
> The thing is that it's not just that emacs redraws _more_ than GTK apps,
> it's that it redraws _at all_ (by `redraw' here, I'm referring to full
> redraws).  IOW, it's a `0 vs 1' problem, not a `1 vs 2' problem.

Emacs does not "redraw" the scroll bars ever, it just tells GTK what values
to use for the scroll bars.  The desicion to redraw is in GTK entirely.
GTK redraws scroll bars by clearing all and then redraw, which is very
primitive.  Emacs probably changes thumb much more than Gedit, as Gedit
counts lines visible, but Emacs counts characters.  But a good scroll bar
should be able to handle this, as indeed Motif, Xaw3d and others do.

	Jan D.

  reply	other threads:[~2003-03-18  5:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14  5:39 Emacs GTK scroll-bar flickering Miles Bader
2003-03-14 10:19 ` Kai Großjohann
2003-03-14 11:52   ` Andreas Schwab
2003-03-14 12:44     ` Kai Großjohann
2003-03-14 13:35       ` Miles Bader
2003-03-14 18:46         ` Jan D.
2003-03-14 20:04           ` Stefan Monnier
2003-03-14 20:35             ` Jan D.
2003-03-17  5:58           ` Miles Bader
2003-03-17 23:26             ` Jan D.
2003-03-18  1:33               ` Miles Bader
2003-03-18  5:39                 ` Jan D. [this message]
2003-03-18  6:15                   ` Miles Bader
2003-03-18  6:44                     ` Luc Teirlinck
2003-03-18  6:54                       ` Miles Bader
2003-03-18  7:05                         ` Luc Teirlinck
2003-03-18  7:56                           ` Miles Bader
2003-03-18  8:09                             ` Miles Bader
2003-03-19  8:48                           ` Richard Stallman
2003-03-18 22:15                     ` Jan D.
2003-03-18 22:42                       ` Kevin Rodgers
2003-03-19  6:05                         ` Jan D.
2003-03-18 23:28                       ` Miles Bader
2003-03-19  1:07                         ` Kim F. Storm
2003-03-19  1:26                           ` Miles Bader
2003-03-19 22:27                             ` Jan D.
2003-03-20  1:19                               ` Miles Bader
2003-03-21 19:06                               ` Richard Stallman
2003-03-26 18:17                                 ` Jan D.
2003-03-27  1:22                                   ` Miles Bader
2003-03-27  6:54                                     ` Miles Bader
2003-03-27 22:12                                       ` Richard Stallman
2003-03-28  1:29                                         ` Miles Bader
2003-03-29 18:38                                           ` Richard Stallman
2003-03-27 18:06                                     ` Jan D.
2003-03-27 19:04                                     ` Richard Stallman
2003-03-20  8:45                       ` Richard Stallman

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=F43BC9E3-5903-11D7-A088-00039363E640@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).