Hi, On Saturday, April 14, 2012 11:05:10 James Turner wrote: > On 14 Apr 2012, at 10:10, Mathias Fröhlich wrote: > > But every image goes through our hands. We can just rescale this under > > certain conditions. At least the uncompressed textures are unproblematic. > > I would introduce some property that is evaluated in the image load > > callback than. Today the chain of readerwriter options should in any case > > provide a simgear options object that contains the property tree that > > could be queried then. > > Ah, I thought many textures only when through osgDB, and we didn't have any > callback or place to make such changes. If we do, then it's easy to add a > property as you suggest.
That's in ModelRegistry::readImage() Alternatively we could traverse the scenegraph of a loaded model and look for textures. That shouold work also. But the model registry thing sounds at first more plausible to me. Greetings Mathias ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel