Re: [Opensg-users] OpenSG 2: SimpleMaterial oddity

[Gerrit V. <vo...@vo...>]

Hi,

On Wed, 2013-03-13 at 15:40 -0500, Carsten Neumann wrote:
> 	Hello Johannes,
> 
> On 03/07/2013 02:20 AM, Johannes wrote:
> > commitChanges() is called and the rebuildState() function is also
> > called. But I can't find the place where the parent ChunkMaterial chunk
> > list is populated.
> >
> > In SimpleMaterial's rebuildState() the _materialChunk is updated and
> > added to the _pState member. Additionally, the parent's
> > addChunks(_pState) function is called which populates the _pState with
> > the parent's chunks found in the _mfChunks container.
> >
> > However, the _mfChunks of the parent is never changed and that is
> > actually what is evaluated in the MaterialChunkOverrideGroup
> > renderEnter() function. Maybe the implementation of this function does
> > make wrong assumptions about the chunks container content?
> 
> hmm, it seems to me MaterialChunkOverrideGroup should iterate over the 
> chunks of the State returned by PrimeMaterial::getState(). That would 
> also make it work with materials not derived from ChunkMaterial.
> This is made a bit tricky by the fact that State does not allow easy 
> iteration over it's contained chunks.

looking at the code it might actually make more sense to let the
material do the work instead of the other way around. Let me look
at it quickly.

kind regards
  gerrit