Hello Johannes,
Johannes Brunen wrote:
>>> I'm not sure if OpenSG 2.0 is also affected.
>> yes, it has a similar problem, but the TextureChunk is deprecated there
>> and replaced with TextureObjChunk and TextureEnvChunk. Anyways I'll
>> change the SFImage to be a child pointer field, then it should handle
>> this automagically.
>>
> What happens to 'osg' files written with OpenSG 1.8 and later on reading
> them back with OpenSG 2.0 with regard to the TextureChunk objects burried in
> the model?
nothing, it remains a TextureChunk and therefore only works if you have
the libs built with -DOSGCOMPAT_ENABLE_DEPRECATED=ON
> I thougth that the 'osg' file format is stable. Isn't it?
no, 'osg' is just an text dump of the tree, 'osb' the binary format is
the stable one. For that TextureChunk is converted to TextureObjChunk +
TextureEnvChunk.
> Are there other classes I can't expect to be usable in the transition.
StateSortGroup is gone (GroupingStage can be used to get a similar
result), the way shaders and FBOs work has changed significantly, but
there are compatibility classes that should provide the old interface.
Off the top of my head these are the big ones.
Cheers,
Carsten
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
