vtkTimeStamp records a unique time when the method Modified() is executed. This time is guaranteed to be monotonically increasing. Classes use this object to record modified and/or execution time. There is built in support for the binary < and > comparison operators between two vtkTimeStamp objects.
Public Member Functions
|unsigned long||GetMTime () const|
|operator unsigned long () const|
|bool||operator> (vtkTimeStamp &ts)|
|bool||operator< (vtkTimeStamp &ts)|
Static Public Member Functions
|static vtkTimeStamp *||New ()|
|static vtkTimeStamp* vtkTimeStamp::New||(||)||
Set this objects time to the current time. The current time is just a monotonically increasing unsigned long integer. It is possible for this number to wrap around back to zero. This should only happen for processes that have been running for a very long time, while constantly changing objects within the program. When this does occur, the typical consequence should be that some filters will update themselves when really they don't need to.
|unsigned long vtkTimeStamp::GetMTime||(||)|| const
|bool vtkTimeStamp::operator>||(||vtkTimeStamp &||ts||)||
|bool vtkTimeStamp::operator<||(||vtkTimeStamp &||ts||)||
|vtkTimeStamp::operator unsigned long||(||)|| const