Paul,
Unfortunately I'm only at version 1.1 :(
Here's the test case I put together for the light point appearance pool in
PaletteRecords.cpp:
Brian
#if 1
// check if parent pool overrides and that the pool exists
if (document.getLightPointAppearancePoolParent())
{
// get parent pool
LightPointAppearancePool * parentPool =
document.getOrCreateLightPointAppearancePool();
// check if not empty
if (parentPool->size() > 0)
{
// use parent's light point appearance pool --
ignore this record
return;
}
else
{
// create a new local pool (not parent)
bool isParent = false;
document.setLightPointAppearancePool(new
LightPointAppearancePool,isParent);
}
}
#else
if (document.getLightPointAppearancePoolParent())
{
return;
}
#endif
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use of
e-mail for such purpose.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"Paul Martz" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
02/23/2007 01:57 PM
Please respond to
osg users <[email protected]>
To
"'osg users'" <[email protected]>
cc
Subject
RE: [osg-users] OpenFlight LightPoint Problem (OpenFlightversion 15.7)
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/
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
