Why doesn't LabVIEW remember resolved conflicts?

[RTSLVU]

This is something that has bothered me probably since the inception of the Project Explorer.

When a project gets "conflits" for whatever reason, from then on every time I load a top level VI from that project I have to resolve the same conflicts. 

Why can't LabVIEW "write this information down" somewhere so I don't have to resolve the same conflicts everytime I open the VI until the end of time.

[cbutcher]

Are you using PPLs or some form of compiled source?

[RTSLVU]

Nope just VI's on my hard drive

[Ben]

You have to save all of the VIs that are involved with the conflicts.

If they are not all saved, the unsaved VI will still remember the conflict and ... bad bad, bad.

A "Tree.VI" that contains all of the top level VIs and dynamic dispatched VI etc. can be helpful since doing a "Save All" for the Tree.VI should update all after the conflict is resolved.

Ben

[RTSLVU]

---

@Ben wrote:

You have to save all of the VIs that are involved with the conflicts.

If they are not all saved, the unsaved VI will still remember the conflict and ... bad bad, bad.

A "Tree.VI" that contains all of the top level VIs and dynamic dispatched VI etc. can be helpful since doing a "Save All" for the Tree.VI should update all after the conflict is resolved.

Ben

---

I have saved and re-saved every VI in this project several times over the years (yes YEARS) this has been happening.

But I just got a new computer and am in the middle of rebuilding my file structure, so maybe it will fix itself that way.

[JÞB]

Well, let's follow Bob's advice and show us a problem project.  Screenshot of the project items view with paths on the right showing.

Almost certainly your project is not flossed.  Look for Swatts blog.  You need to keep your dependancies clean! Dependancies aren't in the project namespace so, they load from the search paths you have in the LabVIEW. Ini often this finds them somewhere else or worse, the paths in SCC don't match the checkout folder.  (   A super PITA with multiple developers using there own locations and worse with auto pop folders).

I do offer "Come to the river" services.  It doesn't take long to get everyone singing from the same hymnal.

[RTSLVU]

How do I show the path in the "Items View" 

[billko]

---

@RTSLVU wrote:

How do I show the path in the "Items View" 

---

Project --> Show Item Paths.

Not very intuitive.

[RTSLVU]

Okay here you go... Now this is on a new computer so all of the dependencies marked (deleted renamed. etc) are in essence deleted. But LabVIEW will not update this no matter how may times I resolve all the conflicts and save the project and all its VI's

[JÞB]

Robert's,  for a forum heavy hitter I'll do the things needed free.

Hit me up PM but, look up Swatts blog too!

Those dependancies need.....there isn't a nice word.  Def+●○ing?