Hi Robert, On 14.10.2010 15:36, Robert Osfield wrote:
I don't think moving texture object selection into SubloadCallback::load would be a good idea as it'd break backwards compatibility - i.e. existing apps will assume that the texture object has been created for it prior to load() being called.Two solutions to allow the SubloadCallback to tack responsibility for texture object assignment would be to: A) Have a virtual SubloadCallback::createTextureObject() method with a default implementation that matches the current implementation. The Texture2D implementation would then in turn would call createTextureObject() then the load() callback methods. B) Have a virtual SubloadCallback::createTextureObjectAndLoad() method that does texture object create and then calls load(). My currently inclination is for solution A being the cleanest. Thoughts? Robert.
Good idea, I thought about something like that, it would be best solution. Can I help you, or you wish to do it yourself? Mikhail. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
