LabVIEW Idea Exchange
Hello all,
The best summary of this idea I can come up with is:
When isolating errors in inheriting classes, the "Error list" window needs improvement so that it is easier to find the root cause of "cascading," hierarchical errors.
I debated whether to post this one, as it's somewhat difficult to explain, and please bear with me as I'm describing the issue from memory and might get a couple of details wrong.
Here it goes:
In many cases I find it difficult to isolate errors in LVOOP classes, especially when I have a hierarchy of several inheriting classes, and even more so when employing dynamic dispatch VIs.
Here's how things might proceed:
- I have a broken run arrow for one of my class method VIs, but the VI reports that class is broken.
- I bring up the error window by right clicking on the broken class and selecting "Show Error Window"
- The "Error list" window contains myriad errors, some of which pertain to the class I'm working on
- All or most methods in the class have errors listed because the class has a broken dynamic dispatch VI
- Inheriting classes with the same dynamic dispatch VIs also report copious errors, citing one or more dynamic dispatch instances of that VI being broken.
- I go up and down the class hierarchy trying to figure out which method is actually causing the error fest
- And on and on it goes...
- In the end, I have so many "false alarm" errors that point in all directions, effectively making the error window almost useless.
At this point, I trace my steps backward to figure out what I did that caused massive cascading error mayhem. Yet, it would be fantastic if the error list window somehow detected the offending method that is behind all of the cascading errors. I don't know what this would look like, but I would love any improvement in this area.
Maybe someone's posted something similar, but I couldn't find it.
Alright, I know everyone is now asking, "What the heck is he trying to say?!" 
That is my best attempt. Feel free to summarize it more succinctly.
Thank you for reading this giant missive.
Jim
