Hello Michael,
On 03/16/2015 10:15 AM, Michael Raab wrote:
> just wanted to detail my question...
> I would like to access some data that is local to a certain stage.
> Stages typically store their data using iDataSlot, which makes access to
> those a bit unhandy.
> My current case refers to the DeferredShadingStage. I would like to get
> access to a certain TextureObjChunk to be able to share it with a
> successive stage.
> So could someone please tell me
> - why this iDataSlot concept was implemented and
many stages have internal objects that depend on the camera (or window)
that is being rendered to - think framebuffer object attachments. In
order to avoid constantly re-sizing these when the same scene is
rendered from different viewports they are stored with the iDataSlot
mechanism which makes them local to the RenderAction - this uses the
assumption that different viewports are rendered with different
RenderActions, but that is often the case.
> - what would be the appropriate approach to access that stage related
> data.
Hmm, I suppose one option could be to additionally store the last used
object in the stage itself. Or perhaps add an interface that allows
access to the data store when given a RenderAction.
Cheers,
Carsten
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
