Hi Robert,
No offense, but this feels more like a hack than my solution. The point
is, that the original solution simply does not move any information to
the outside. I agree that is not the cleanest solution to open up
multiple code paths here.
What I don't get is the initial design. In my understanding it is bad
design not to call the original implementation (i.e. findFile), as a
user adding callbacks will fail. So chain of responsibility is broken here.
You are right however: Passing the information would solve my problem
since I only need to know which files are missing.
Also I want to point out that I'm not the only person having this problem.
cheers
Sebastian
Hi Sebastian,
One possible way to get things to work without modifying the core OSG
would be to have a custom FindFileCallback and custom
ReadFileCallback. The FindFileCallback would try the normal search
for the file and on failure rather than passing back an empty string
could pass back "FILE_NOT_FOUND:filename" and then the custom
ReadFileCallback could filter fiter for "FILE_NOT_FOUND:" and then
obtain the filename from the rest of the string.
Robert.
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
