b3c/MAF2 — pull request #21 by besoft (2012-11-27 13:55:09+00:00)
Title: Open maf 2 2

When setting a new current time to the whole VME data tree (see mafVME::SetTreeTime method or VME_TIME_SET event), the current OpenMAFsolution allows time inconsistency for procedural VMEs that depend on multiple other VMEs, i.e., when the Update of a procedural VME is called, each of its dependant VMEs may have different time.

The reason for this behaviour is that the method mafVME::SetTimeStamp, which is called to set the time to one VME, notifies listeners of this VME that the time has changed and any of these listener, e.g., mafPipeSurface, may call Update method in reaction. By the time the Update is called, VMEs lower in the tree still contain the previous time.

I have resolved the problem by setting time for the whole VME data tree first and then notifying all listeners at once.