Hi Stefan, The data will be attached and handled by the ObjectMap . The question now is what would be the best way to update aka commit / sync these data on a per frame basis since there are data that would have to be updated on a per frame basis ( video timestamps for example ).
That's why I am thinking of exposing an update function through seq::app::MasterConfig between frameFinish and frameStart so that the user can set a dirty state of the data on a per-frame basis. Basically this is already happening in ViewData::update but I would prefer to expose a similar mechanism through seq::Application instead. As for #227 I am not entirely sure if it is 100% complete.. It does expose the full internal ObjectMap interface for the application and renderer i.e register/deregister, map/unmap but this <https://github.com/Eyescale/Equalizer/issues/277#issuecomment-42765444> is still unclear to me.. Obviously I have failed to describe properly what my question / problem is in that case since your answer <https://github.com/Eyescale/Equalizer/issues/277#issuecomment-42768120> is obvious to me but it doesnt explain my problem :) This is also why I asked for an illustration if you had some time of registering / mapping an arbitrary number of objects based on the example that I have created there.. :) Anyways, I am gonna get back to this with some fresh eyes and hopefully its gonna be clear.. Obviously if you think that what is there already is enough for you I can open a pull request any time.. Thanks, Petros. -- View this message in context: http://software.1713.n2.nabble.com/Updating-various-data-to-clients-tp7585908p7585953.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
