>>> "Ken Hayber" <ken@...> 24/Nov/2004 22:46:00 >>>
>Stephen Watson said:
>> Tony Houghton <h@...> wrote:
>>> Have you tried GDK_INTERP_BILINEAR? That's what the developer docs
>>> recommend as the best compromise.
>> It's not much slower than GDK_INTERP_NEAREST and doesn't suffer from
>> blurring. Looks like I'll be using that one.
>BILINEAR is what it has always been. I'm the one who submitted the
>to Thomas. I found many images that were pixelated and had poor
>transitions with BILINEAR. HYPER works much better for me. I guess
>but I've never seen any blurring effects unless the image was very
>quality to begin with (or was stretched a lot).
Attached is the code I used to check the various methods. It tests the
case where it doesn't
need to scale the image, which is why the HYPER behaviour is puzzling.
I used a
background image generated by xplanet for the screen size.
Here's the results for a SPARC Solaris system:
near: user 0.05s, system 0.01s
bil: user 0.46s, system 0.03s
hyper: user 1.30s, system 0.00s
near and bil appear the same as the original image, hyper suffers from