LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Ben_Phillips

Error dialog to have option to take you to the VI that threw the dialog

Status: Declined

Any idea that has received less than 7 kudos within 7 years after posting will be automatically declined.

Even to this day, I still use the Simple Error Handler, for times when I'm writing throwaway code, normally when I'm stress testing a new API.

 

When that dialog is thrown, you should have the option to bring up the block diagram of the VI where it occurred.  Kind of the way breakpoints are done.  Just another button on the dialog that says "Take me there."

 

This is not a high impact improvement, but it also has no chance of hurting anything, and I think an intern could do this.  I guess I could just do it myself, but it should be baked into LV.

 

 

~~~~

Post edit:  holy cow!  Your spell checker is from 1996.  Terrible!  You guys have the best technology, I'm shocked by how retarded it is when you hit the 'Spell Check' button.  What does that message even mean?  I'll translate:  Do you not want me to not undo something that may not have happened?

3 Comments
shb
Active Participant
Active Participant

Great idea.

Doing it yourself is troublesome, because finding the correct SubVI instance in the calling VI is somewhere between troublesome and impossible.

 

AristosQueue (NI)
NI Employee (retired)

Both the General Error Handler (GEH) and the Simple Error Handler (SEH) are written to be used in end-user code. It is generally bad idea to hand your users a button that opens your diagrams, which is why those two VIs do not have that facility.

 

Creating a third error handler that is designed specifically for debugging would be possible. We'd probably adjust a lot of functionality for such a node. It is a good idea worth considering.

 

In the meantime, you could add this ability to the SEH yourself with very little programming -- all the VIs are open (no passwords). Add a button to the front panel and in the event structure, handle its click -- read the first line of the source string, wire the name to Open VI Reference (you can wire a string instead of a path to open by name) and then open its panel (method node).


> Post edit:  holy cow!  Your spell checker is from 1996.

 

Excellent. I'll tell the rest of R&D that the time machine is working. That "1996" is actually "1996 p.a." which stands for "post-apocalypse", which in our calendar is roughly 3100 a.d. That's just how the language changes over >1000 years. Not a bug.

 

 

🙂

 

Darren
Proven Zealot
Status changed to: Declined

Any idea that has received less than 7 kudos within 7 years after posting will be automatically declined.