From: "Jan D." <jan.h.d@swipnet.se>
Cc: Kai Gro?johann <kai.grossjohann@uni-duisburg.de>
Subject: Re: Emacs GTK scroll-bar flickering
Date: Tue, 18 Mar 2003 00:26:42 +0100 [thread overview]
Message-ID: <3E7659B2.2090608@swipnet.se> (raw)
In-Reply-To: <buovfyiv8jj.fsf@mcspd15.ucom.lsi.nec.co.jp>
Miles Bader wrote:
> Hmmm, today's CVS seems _slightly_ better -- at least, cursor movement
> doesn't cause flickering. However, the behavior when the buffer size
> (or window configuration, etc) changes is if anything, worse now: it
> looks like whenever the scrollbar gets updated (even by a single
> character change in the buffer), it's getting completely cleared and
> redrawn about 4 or 5 times, with each redraw being very obvious and slow
> (this is certainly exacerbated because I'm using a pixmap theme, but
> this theme is not a problem with other GTK apps).
>
> Something really seems drastically wrong here, since other GTK apps [I'm
> using `gedit' for comparison] have basically no flickering, slowdown, or
> obviously excessive redraws when they update the scrollbar. It seems as
> if emacs is somehow completely regenerating the scrollbar whereas other
> apps are using some sort of interface that allows incremental updating
> or the like.
I made some changes, please try them out.
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.
Jan D.
next prev parent reply other threads:[~2003-03-17 23:26 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. [this message]
2003-03-18 1:33 ` Miles Bader
2003-03-18 5:39 ` Jan D.
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=3E7659B2.2090608@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=kai.grossjohann@uni-duisburg.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).