Do not save dependencies when using "Save all (this Project/Library/Class)"

[maxwellb]

The tendency of LabVIEW to indicate that 5 or 10 VIs have been changed for every VI actually edited makes maintiaining organized, legible version control logs difficult. To be kind to my co-developers, whenever possible, I try to keep the number of spuriously modified VIs down by intentionally not saving VIs that do not need to be saved. This would be a lot easier if the "Save all (this Project/Library/Class)" menu item behaved as it sounds intuitively. Currently, it functions to save all of the items in the Project/Library/Class, as well as their dependencies. In 99.9% of all cases, I did not intend to modify any dependencies. If I had intended to work on them, they would be in the library or project.

This idea is to have the "Save all (this Project/Library/Class)" menu item save only items inside the Project/Library/Class, and not their dependencies.

[crossrulz]

If you didn't edit those dependencies, then why are you saving them?  If you didn't make any changes, then LabVIEW will have no reason to save.

It is also sounding like you need to use the Separate Compiled Code option in the VI properties.  This will prevent recompile saves from messing up your version control.

[maxwellb]

Separate Compiled Code is a good step in the right direction but it is not perfect. For example, the latest version still registers a change if a typedef used by a VI changes. In my opinion, the more tools there are to help not revision a file when you didn't intend to, the easier development of a large, multideveloper project in LabVIEW will be.