Hi, is it intentional, or a bug that the MTime of the nodes is not saved with the project? Or maybe they are saved but not restored.
Is it related eventually to the bug that I reported recently? (The mitk::Image properties are saved into the scene file, but are not restored when the project is opened.) This would be quite important here. In my app the user can perform an analysis of several steps (a ctkWorkflow), and he/she can save the project. If the project is reopened, the user should be able to go through the steps again, eventually changing some parameters, and the calculation should be performed again only if the MTime of the inputs is newer then that of the outputs. However, the MTime values are different every time that I open the project. Can you suggest some workaround for this, eventually? thanks, Miklos ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
