Hi Sukender, I've been pondering the issue of proxy images overnight and starting to wonder if we shouldn't be tackling it in quite a different way. Rather than lower integration with osg::Image via a callback I am thinking that perhaps a Node update/cull callback that loads all the proxy images for it's subgraph would be more appropriate.
Such a callback could have a list of osg::Texture that need loading and when traversal hits this node it could load them and then continue traversal of the subgraph or run the load in a back ground thread and not do the traversal until that thread has loaded all the images. This way you could load the sub graph and only have it appear on screen once everything has loaded and make it possible to avoid frame drops due to loading. One could still have the immediate load and accept the frame drop, one could simply have a single callback with two mods of operation or two different callbacks for each case. As well as enable constant frame rate support this callback approach would keep all the required code localized in the callbacks, one wouldn't need to modify osg::Texture/osg::Image. Thoughts? Robert. _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
