Hi Carsten,

>       Hi Andreas,
> 
> Andreas Zieringer wrote:
> 
>>Hi Carsten,
>>
>>this hack was necessary to load old 1.x osb files. In 1.x the 
>>MaterialChunk has a internal field, not sure about 2.0 but I think there 
>>is no "real" internal field anymore.
> 
> 
> hm, I just looked through CVS history but could not find such a field in
> OSGMaterialChunkBase.h, but I guess I'll just leave the hack in.

yes this field exists in every StateChunk I think it comes from the 
Attachment class.

> Something different on NFIO:
> There is the postProcess operation that seems to do some conversions
>>from old formats and apparently is allowed to delete FCs along the way.
> Now, my question is: shouldn't this happen *before* calling
> chargeFieldPtr and update the id map correspondingly ?

well I'm not sure if this works but right now it works fine and it is 
safe because I use the fieldcontainer id's and not the pointers. There 
is a comment in OSGNFIOBase.cpp line 279

Andreas

>       Thanks,
>               Carsten
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Opensg-core mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensg-core
> 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core

Reply via email to