Thanks for your input, Marcus.
> ... then file C inherits file A's palette because that is the
> effective palette for file B.
Good, I believe this is what our OpenFlight plugin does (at least, that was
my intent when I added support for palette overrides).
> The fallback for a truely missing palette is for a file to
> use its own palette.
Sounds very reasonable. I don't believe our OpenFlight plugin does this
currently. The logic for this would be something like:
IF ext ref record says use parent palette
AND parent palette exists THEN
use parent palette
ELSE
use child palette
And that needs to be done for each of the palette types, not just light
points.
Brian, are you up for implementing this? The changes should be localized to
ReaderWriterFLT.cpp, IIRC.
-Paul
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
