Hi,
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
- what would be the appropriate approach to access that stage related data.
Thanks in advance
Michael
Gesendet: Montag, 16. März 2015 um 12:30 Uhr
Von: "Michael Raab" <[email protected]>
An: [email protected]
Betreff: [Opensg-users] Stages - DataSlotId
Von: "Michael Raab" <[email protected]>
An: [email protected]
Betreff: [Opensg-users] Stages - DataSlotId
Hi,
why are Stages typically storing their data via _iDataSlot?
Thanks,
Michael
------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
