Hi Petros, On 10. Jul 2014, at 11:12, "Petros.Kataras [via Software]" <[email protected]> wrote:
> 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. Ok, that makes sense now. I guess you wouldn't set a dirty state but rather do processing which happens to make some objects dirty. > 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 is still unclear to me.. > Obviously if you think that what is there already is enough for you I can > open a pull request any time.. I would guess that you have a use case against which you validate the code. I'll review it carefully, but won't have the time to create a test or example. Cheers, Stefan. signature.asc (858 bytes) <http://software.1713.n2.nabble.com/attachment/7585954/0/signature.asc> -- View this message in context: http://software.1713.n2.nabble.com/Updating-various-data-to-clients-tp7585908p7585954.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
