Hello,
On 12/07/2010 07:41 AM, Sebastian Till wrote:
> I am still using OpenSG 1.8, wrote a small multithreading application with
> osg::Threads and have some troubles with StatePtrs, TextureChunkPtrs and
> the like as member attributes of Material classes.
>
> My question is: Why is the StatePtr _pState of the Material class not put
> into an SField?
State is what is used to do the actual rendering, Material keeps this as
a cache to avoid having to recreate it all the time.
Putting it into a field would mean it would get copied between aspects
when syncing them. All the information to build the State is already
contained in the other fields and moreover after a sync they are used to
rebuild the State object there is no need to sync it as well.
> The same questions fits for the _materialChunk and the _blendChunk
> attributes of the SimpleMaterial class as well as for the _textureChunk
> and the _texGenChunk attributes of the SimpleTexturedMaterial class (and
> maybe some others, too).
Basically the reason is the same, these things are caches for
information derived from fields of the classes they belong to.
What are you attempting to do and how are these members causing problems
for you?
Cheers,
Carsten
------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
