10-03-2018 11:24 AM
This has been bugging me for several versions now. I keep expecting the next LabVIEW version to have it, but no ... it never does. Perhaps this is my fault for not speaking up earlier ... but I thought the idea was so obvious I didn't need to ... of well, I was wrong ...
When you drop a probe on a wire for the error cluster, why can't you right click the error cluster in the probe window and choose "Explain Error..." like in the main menu? Why do I have to copy the error code to the clipboard, open "Explain Error...", and then paste the error code in order to see the explanation text?
WHY??????
This is so obvious. Please just do it NI. Please.
If you agree, please add to this post so NI will pay attention. I can't be the only one frustrated by the lack of this feature. I just can't be.
Walter
10-03-2018 11:39 AM - edited 10-03-2018 11:42 AM
The LabVIEW Idea Exchange is open for business... and although I agree that default probes could be smarter (How about the ability to show more then one element in an array probe???), it seems that probe enhancements were met with much resistance.
R&D patrols that forum and ideas with high kudos amount may end up in a future release! (And you might even get credit for the change in the "What's new?" section!)
10-05-2018 05:49 AM
What I often miss is the "Explain Error" option in an array of error clusters...
But the idea exchange is the place for requests like this (if they aren't posted already of course):
So kudo those, and it might happen some day...
10-05-2018 08:06 AM
Two options.
1 create a custom menu shortcut to "explain error" from the tools options menu shortcuts dialog. Kudos for showing directions with snips
2 pop out the probe from the probe watch window.. last I thought, explain error work there... haven't tried recently .. I stopped writing bugs a while back:D
Did I only say 2? Oops
3 customize your own error probe to call that dialog ... that would be neat and a great custom probe to share.
4 stop writing code that throws errors....
10-05-2018 08:54 AM
Best idea I've heard in a long time. Put it in the FAQ!
@JÞB
Jeff·Þ·Bohrer wrote:
... 4 stop writing code that throws errors....
-Kevin P