LabVIEW Idea Exchange

[#1]

Placing a visual mark (e.g. a red dot) next to broken Vis in the project explorer could help to identify possible issues in an easy way.

[#2]

If the VIs are loaded into memory, then the broken VIs appear at the top of the list in the error window with a red X. Isn't that good enough?

[#3]

I like it. Even though broken VIs are listed in the error window, this is just another way to spot them. And since the project explorer already has the information it should not be very difficult to implement.

[#4]

I'd also like to add a TODO note to VIs in the project explorer. At the end of a day, to prevent forgetting my TODO labels, I drop an unwired numeric operation next to them. find broken VI -> find todo note.

[#5]

Two things I don't like about this:

1. The VIs in my project are generally in a hierarchy. For broken VIs I prefer a flat list. If I'm looking for broken VIs it's probably because I intend to fix them, so I might as well be going through them one at a time.
2. I really don't want the project window to get too noisy. Maybe if it had additional columns, this could be an optional column, but I wouldn't want it as an icon or an overlay.

[#6]

I can see your point about the noise. Just to be clear I wouldn't want this idea to replace the list of broken VIs in show errors.

[#7]

---

tst wrote:

Two things I don't like about this:

1. The VIs in my project are generally in a hierarchy. For broken VIs I prefer a flat list. If I'm looking for broken VIs it's probably because I intend to fix them, so I might as well be going through them one at a time.
2. I really don't want the project window to get too noisy. Maybe if it had additional columns, this could be an optional column, but I wouldn't want it as an icon or an overlay.

---

Maybe something like Show More VI Properties, just adding another column for compiled/in-mem/broken?

[#8]

Two things I don't like about this:

1. The VIs in my project are generally in a hierarchy. For broken VIs I prefer a flat list. If I'm looking for broken VIs it's probably because I intend to fix them, so I might as well be going through them one at a time.
2. I really don't want the project window to get too noisy. Maybe if it had additional columns, this could be an optional column, but I wouldn't want it as an icon or an overlay.

[#9]

> And since the project explorer already has the information it should not be very difficult to implement.

The project doesn't already have this information. The project lists all the VIs in your project, whether loaded or not. It doesn't know anything about the broken status of VIs that are not loaded.

[#10]

I meant the project explorer as in the whole IDE, and that the program has a list of broken vis in the error window. I know that the project file itself is just a list.

[#11]

@AQ, I see what you are getting at. Since the project explorer can only list broken VIs that are loaded it would not be able to mark/show/highlight broken VIs that are not loaded. Because of this inconsistency I am revoking my support of this idea. It would be a good idea if it were possible so I will keep my kudos on it just in case you guys can figure out how to do it. I need to learn not to post with incorrect blood/caffeine levels

[#12]

I'd like the entire path to the broken VI(s) tagged in some way to make it easy to find them. For example, make the foreground text of all path elements to the VI and the VI itself in red. So for any broken VI under "My Computer", "My Computer" would be in red along with all folders and lvlibs to that VI. I currently run the "Mass compile" option on the "Project: XXXXX" run-time menu to find all broken VIs in my project. I like it because it only compiles my project files, however, it doesn't display the dialog box with the logging option as the one under the "Tools...Advanced..." does. I like the logging option of the mass compile on the "Tools...Advanced..." menu but it compiles every VI in the path you specify rather than only your project files.

Or how about populating the "View...Error List" with the "BAD VI" results from the Project Mass Compile??