Hi Miklos,

It is indeed intentional not to store the MTime information. The MTime is a 
relative counter, independent(!) of system time and other global counters, 
which starts at value 0 at each start of an application. In fact it is a long 
variable held by ITK that is increased every time an itk::Object gets updated. 
Using some pre-defined MTime values ( i.e. from previous runs of the 
application as you intended ) can prevent the filter from updating even if an 
update was necessary.

As a workaround - you can define a property which somehow describes the 
relationship between the nodes. For this you have to assign this property to a 
DataNode, because of the issue you have reported for mitk::Image properties, 
and save the project. This property will be restored after loading the project 
file again.

Best,

Jan

-----Ursprüngliche Nachricht-----
Von: Miklos Espak [mailto:[email protected]] 
Gesendet: Dienstag, 6. Dezember 2011 14:04
An: mitk-users
Betreff: [mitk-users] DataNode/Image MTime not saved by "Save Project"

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

------------------------------------------------------------------------------
10 Tips for Better Server Consolidation
Server virtualization is being driven by many needs.  
But none more important than the need to reduce IT complexity 
while improving strategic productivity.  Learn More! 
http://www.accelacomm.com/jaw/sdnl/114/51507609/
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to