On 21 Apr 2013 Rob Kendrick wrote: > On Sun, Apr 21, 2013 at 10:06:49AM +0100, Richard Porter wrote: >> I don't think there's anything I can do other than that. I was >> wondering whether there's a design reason why NS doesn't keep a copy >> of the resized image in its cache, which would save a lot of >> processing time in such circumstances.
> Choices -> Cache -> Enter suitably large number. Shoving 40MB in here > makes the page scroll smoothly where with the default value it did not. I've tried 40MB but it doesn't make any difference. I did quit and restart NS in case that mattered, but as soon as I hit the large image files it was like scrolling through treacle. -- Richard Porter http://www.minijem.plus.com/ mailto:r...@minijem.plus.com I don't want a "user experience" - I just want stuff that works.