- May
- 608
- 4
Charles,
Please consider adding a fourth argument to @CMPTIME to work as follows:
The reason is that I've discovered that when copying a file from one device to another, sometimes the timestamps differ by a small amount. Today I discovered a pair that differed by 440 milliseconds and another that differed by 421 milliseconds. Ideally, the tolerance should work in both directions, but if it's easier for it to work in only one direction, that would be acceptable.
Please consider adding a fourth argument to @CMPTIME to work as follows:
Code:
Syntax:
%@CMPTIME[file1,file2,which,tolerance]
file1 the first file to examine
file2 the second file to examine
which A, C, or W; the default is W
tolerance number of milliseconds (or maybe seconds) of tolerance to use when comparing timestamps, default is zero.
The reason is that I've discovered that when copying a file from one device to another, sometimes the timestamps differ by a small amount. Today I discovered a pair that differed by 440 milliseconds and another that differed by 421 milliseconds. Ideally, the tolerance should work in both directions, but if it's easier for it to work in only one direction, that would be acceptable.