Hi Petros, On 7. Jul 2014, at 15:37, Petros.Kataras [via Software] <[email protected]> wrote:
> i.e data could be timestamps of videos for syncing across multiple nodes or > attributes of a particle system and so on .. > > Should all these stuff be handled from ViewData::update() in sequel terms ?? Very likely yes, since this gives you consistency wrt the rendered frame. You could update your objects using Collage functionality only, but this would run asynchronous to the rendering. For global state there is also the FrameData. In general people tend either to use a central registry (aka co::ObjectMap) or a tree-like structure of objects attached to FrameData or View. I'm not sure if that answers your question. Cheers, Stefan. -- http://www.eyescale.ch https://github.com/Eyescale/ http://www.linkedin.com/in/eilemann signature.asc (858 bytes) <http://software.1713.n2.nabble.com/attachment/7585915/0/signature.asc> -- View this message in context: http://software.1713.n2.nabble.com/Updating-various-data-to-clients-tp7585908p7585915.html Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
