Hi Jan, thanks for the explanation!
Indeed, I thought the MTime depends on the system time, the name suggests this. If its just a counter, it cannot be used for my purpose, anyway. Now I store all the metainfo in the nodes, also to see them in the Property list view. So the bug I reported does not affect me, anymore. Well, I will think about it. I do not see a trivial solution now. Best, Miklos On Thu, Dec 15, 2011 at 3:06 PM, Hering, Jan <[email protected]> wrote: > 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. ------------------------------------------------------------------------------ 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
