Robert Osfield wrote: > Both, the two were intermixed in the case of the recursion code. Is > this required? Can it be be totally independent? > I'm happy to integrate one feature at a time, so perhaps tackling teh > recursion first would be appropriate then add the suffix addition to > this.
Actually osgconv is mostly oblivious to the suffix, however it made use of a method I added during the suffix work, getCombinedFileNameWithSuffix(). In the absence of the pseudoloader suffix capability, this method would simply be getCombinedFileName(), and it is a DRY refactoring to extract the filename-assembly code normally locked inaccessibly within PagedLOD::traverse so that osgconv can see what full pathname the PagedLOD would like to load the child from. I could refactor this so that recursive osgconv can move forward without pseudoloader suffix support. My latest suffix-support proposal in "PagedLOD/ProxyNode design discussion" would have a getCombinedFileName() method, so maybe we should decide that issue first, and osgconv would basically slide in right afterward. > Robert. -- Chris 'Xenon' Hanson, omo sanza lettere Xenon AlphaPixel.com PixelSense Landsat processing now available! http://www.alphapixel.com/demos/ "There is no Truth. There is only Perception. To Perceive is to Exist." - Xen _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
