On Tue, Oct 09, 2007 at 05:25:09PM +0200, Johannes Hofmann wrote:
On Mon, Oct 08, 2007 at 10:23:22PM +0200, Matthias Franz wrote:
It is slow, because the default linesize (the amount a scrollbar scrolls when pushing on the arrow is 1. I could change that, but what would be a reasonable value? Apart from that it should not consume all CPU time. It doesn't here. On which html page do you test?
It occurs on any page where you can scroll.
Speaking of scrolling, if I hold down PageDown or PageUp, a large page of text often can't keep up. The scrollbar will be, say, at the extreme bottom, but the text might stop around the 80% mark.
Today I noticed that other features of dillo-fltk are also slower than before. For example, I get approximately a 50% CPU load just by moving the pointer repeatedly back and forth over a link so that the pointer constantly changes from the "arrow" shape to the "hand" shape and back. When I do this with the old dillo the CPU load remains around zero. (I have an AMD Athlon prcessor running at 660 MHz.) I don't know whether this is a problem with dillo, fltk or just with my machine (Debian Etch).
Do other people observe this problem as well?
Now that I know to look for it, yes. It seems to depend on how large the textblock is that I move over. Commenting out Textblock::motionNotifyImpl() made no difference, and I don't know the upstream code well enough yet to chase down the problem efficiently...