On Thu, 4 Mar 2004 netsurf(a)sparkplug.org.uk wrote:
On 4 Mar, John-Mark Bell <jmb202(a)ecs.soton.ac.uk> wrote:
> Hopefully, this is now fixed...
> As an aside, I'm fairly seriously considering binning the OS JPEG renderer
> and using the libjpeg code for all JPEGs. Right now, the libjpeg code is
> only used when the OS can't cope. The downside to this is that memory
> usage will increase a small amount.
As a Select user I would like you to continue to use the OS renderer, but
maybe have a option in the choices window to select what to use like
I was waiting for that response from someone ;)
It could well end up that we do be like Browse and have an option
selectable by the user. Part of the issue here is that the "old" (ie RO !=
Select) JPEG renderer is prone to mistakes. For example, we've seen a
number of cases where the OS believes it is able to cope with the image
when, in reality, it can't. Simply using libjpeg for everything would
Also would it be possible to set the quality of the images to be
when using the built in renderer in Select as you can with the built in
Select image viewer.
If it's not possible to do this via the standard jpeg SWIs, then I doubt
it. It's annoying enough having to maintain code for two separate
renderers, let alone three.
Of course, I reserve the right to change my mind at a later date ;)