> 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.
Exactly.. > 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. Right now there is minimal example ( inside seqPly ) illustrating registration and committing of master instances UUID's to the slave ObjectMap. Mapping appropriately is where I am losing track. Would you like to review what is already there i.e should I already open a pull request for you to review or would you prefer a more concrete use case ?? Cheers, Petros -- View this message in context: http://software.1713.n2.nabble.com/Updating-various-data-to-clients-tp7585908p7585956.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
