Jorge wrote:
[corvid wrote:] With clear_double_buffer(), I hit page down on an already-loaded page. It takes four seconds to draw the screen of text (well, and then it performs a redraw for another three or four seconds).
(Just wanted to mention that the redraw became rare when I tried running with it some more, and went away when I paid enough attention to try to figure out what conditions triggered it...)
If I comment out clear_double_buffer(), it takes no perceived time.
Some days ago (and before) I've tested dillo2 without Johannes' patch, in a Thinkpad 380Z, and also with a 385XD. Both render antialiased fonts much faster than you describe.
[Johannes wrote:] There is two things I don't understand. First, antialiased fonts seem to be extremely slow on your system. What about the test programs from fltk, are they usable? Or other programs that use antialiased fonts?
Second, commenting out clear_double_buffer() seems to make it faster - not just reducing flicker.
Considering the rendering speed in my old laptops, and what place describes, I guess drawing is taking different function paths in FLTK depending on double-buffering and the detected capabilities of X (something similar to what happens when using the VESA path instead of the native mode with some video cards).
Antialiased fonts are extremely slow on his system, and that looks like something fishy is going on.
Sounds like I'll have to play around with my configuration. I expected it to be slow, so nothing ever drew my suspicion...