On 9 Aug, Richard Wilson wrote:
Jeremy C B Nicoll <Jeremy(a)omba.demon.co.uk> wrote:
> In article
> John-Mark Bell <jmb202(a)ecs.soton.ac.uk> wrote:
> > Alternatively, it's a result of Display->Render->Buffer all
> > being selected. This does slow NetSurf down somewhat considerably (it's
> > off by default)
> When would use of the buffering option be sensible?
My advice would be to always have "Buffer animations" turned on, and never
have "Buffer all rendering" on unless you have a fast machine or really
really hate flicker. Incidentally, the buffering of animations will also
cause text areas to be buffered and any flicker removed - the documentation
is currently incorrect in this respect.
An simple example of the difference it makes can be seen via a site such as
. Load the page then scroll about using Page Up/Page Down
(so you get a full page drawn each time) to see the difference between the
Speed is noticeably slower when buffering is used as the relevant area of
the screen is grabbed as a Sprite, this is then drawn to, and then finally
the Sprite is plotted back.
On that site I find that without buffering it seems much slower and is
much more annoying since it redraws everything from the background
forward. With buffering on it's quite nice, but I was very surprised to
note that it's slower than O2 in either mode, both in initially loading
the page and all its graphics, and then enlarging the window/ scrolling
around in it. Is there something about this particular site that makes
Netsurf slower than it normally might be, or is rendering still a work
(On an Iyonix, build 09 Aug 17:15)
Sendu Bala http://sendu.me.uk/
| Tori, Kenshin, DNA and my Iyonix
"I tell you with no ego that this is my finest blade. If you should
encounter God, God will be cut."