Changes to sub-components of components of projects shouldn't force change to project file itself

[_carl]

I often use LabVIEW projects.  Projects may contain libraries, classes, etc.

Changing the contents of any component (such as a library) within a project causes the project file to change -- even though the project definition itself shouldn't have actually changed. For instance, if this is my project:

and I delete a VI that is inside an .lvlib, the project file itself claims to have had an attribute change:

In theory, this top-level project change isn't necessary -- since the project should just reference the library, and only the library should reflect a change.

These unnecessary file changes make it trickier to deal with source control, merging code, tracking changes, etc, along with adding one more file that you get prompted to save every time you close a project.