Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.
We have a rather large code repository and are currently making a step-by-step switch to a newer LabVIEW version. Many of the VIs in question are used on Real-Time targets. These are automatically saved whenever deploying. Until now I have been using a tool of mine to parse entire directories of files and compare them to base versions in our SVN repository, automatically reverting those with no "real" changes. We have branches open in both the old LV version and the new LV version in order to maintain bugfixes for customers unable or unwilling to upgrade their LV version.
I can choose to ignore FP cosmetics, BD cosmetics and so on but what I cannot ignore is LV Version. I now have a situation where I need to commit upwards of 300 VI files where the vast majority of them are unchanged except for saving in the new LabVIEW version or manually sift through lots of VIs in order to retain these VIs in their original version.
I would love to have an option to allow LVCompare ignore this kind of change so that we can easily automate this kind of operation.