I'm using the latest beta version 0.6.5.6000 Unicode 64
I use the "Tag Matching States/Not Calculated" to set tags. However, using this feature fileverifier fails to tag the first entry that has not been calculated .. It always begins tagging on the second entry that has not been calculated. So I must manually go back and tag the first entry.
This problem may have something to do with the process I use for tagging. I am calculating hashes on a long list of files. Since the process takes several hours I usually stop the calculation after an hour or so, to save the hash file .. I then use "Tags None" to clear the tags and use the "Tag Matching States/Not Calculated" to set the tags on files not yet calculated before restart.
The file that fails to get tagged was the last file running (getting its hash calculated) prior to stopping FileVerifier. Since I stopped FileVerifier mid-process, this file did not get its hash completed ... However, even though this file has no calculated hash ... its tag does not get set when using the "Tag Matching Status/Not Calculated". Hope this is clear.
The latest beta is v0.6.6.6050.
I tried to reproduce the problem but could not (using v0.6.6.6050). I used sufficiently large files so that I could be sure I interrupted the process in the middle of the hashing operation.
When you do this, does the "Verification" column actually show "Not Calculated" for the item that is not being tagged?