LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
cancel
Showing results for 
Search instead for 
Did you mean: 

Separate icon for broken dependency

Status: New

What is wrong with this VIs diagram?

 

Broken arrow.PNG

Nothing! It's a broken dependency:

Broken dependancy.PNG

 

It would be nice to see the difference without having to open the error dialog:

 

Broken Dep.png

 

Graphics should be improved...

 

The normal broken arrow should have priority over the other. First fix the VI, then the dependency... Wouldn't mind two icons, one for broken VI, one for broken dependency.

1 Comment
Proven Zealot

LabVIEW NXG experimented with this. I don't know why they ultimately decided against it. Let me ask around.

 

It would be kind of a pain to implement in LabVIEW purely for technical reasons... the button bar is one of the oldest not-yet-refactored parts of LV C++ code. I hate going in there myself. So if there's any excuse to not do it, you can be sure I'm looking for it. 🙂