Hi Robert, Sorry, I don't know which problem you're asking about. I currently have things working fine with my own modified code. It appears all the changes I have made to FileUtils.cpp can be accomplished with a callback. I don't see a way to do my Registry changes with a callback.
A new problem showed up recently with the changes you made to exclude current working directory from the default search path. Without this, my modified OSG gets trapped in endless loops where OSG looks for an archive in itself or other archives in an endless loop until it crashes. My current workaround is to add . to the start of my path, but I would like to find a better solution. Watch out for that gotcha if you keep working on this. I wanted to get back to working on this topic in a week or so and try to come up with other options. Your new idea sounds like it has good potential. I would still like a way to search multiple archives for regular files and internal references if you see an opening for that. If your new ideas need testing please send the code and I'll stress test it. - Terry > > Hi Terry, > > I've been wondering about archive functionality, in particular about > the reading of file internal references such as reading the imagery > referenced by a scene graph where both are stored in the same archive. > The intent of the osgDB::Options support in ReaderWriter's is that > nested references should by handled by prepending of the path to the > parent file to a locally cloned osgDB::Options object that is then > passed on when doing the readImage(..) etc call. I haven't done the > testing yet to confirm the behaviour in the context of Archives yet > but what in theory should be happening is that the archive should be > added to the Options object on access to it, and suspect this isn't > happening for all usage models. > > Could it be that the problems you are seeing a related to this issue? > I'm hopeful that if we sort out the proper prepending of the archive > path to the Options object we won't need to intrusive changes to > osgDB::Registry that you've had to make. > > Robert. > _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
