Re: Mipmap filtering

[Frank C <li...@si...>]

On 3-Jun-04, at 10:47 PM, Joseph J. Strout wrote:

> He also mentioned the possibility of anisotropic filtering, but said 
> that would require some discussion, so I'll leave it to him to get 
> that ball rolling if he thinks it important.

Ideally anisotropic filtering would be implemented as a separate 
property of a view, but it could also work as three additional 
Quesa-only filter modes that are converted to hardware specific values:

kQATextureFilter_Anisotropic_Fast
kQATextureFilter_Anisotropic_Mid
kQATextureFilter_Anisotropic_Best

Hardware with a maximum anisotropic range of 8 would use values of 
2,4,8, a maximum of 16 would use 4,8,16 etc. You loose some precision 
on higher-end cards, but it should still work reasonably well without 
adding an additional entry point. I've actually seen many anisotropic 
implementations use a simple toggle (!) so this would certainly offer 
enough control for most uses.

This feature isn't all that critical to me personally, but I'm willing 
to do the grunt work if we can agree on the implementation.

Frank.