Yes, I refer to the "Error List" (VI Menu -> View -> Error List (Ctrl + L))
To clarify the idea let us take an example: A LV project with 100+ files, 2+ targets and 3+ developers working on it. Useful information is to know if there is a broken VI in the project. (This info can be easily extracted using Execution State property of a VI.) However, more useful info would be to know "Why a VI is broken". Maybe it is just a “trivial” error – e.g. "missing shared variables" or something like that. An additional advantage of having this info up-front:
This info could allow us to automate filtering, selecting, tracking and sorting VI errors in a LV project. All in all we could save time 🙂
I like this idea because it would allow someone to see all vis broken in their hierarchy (which can be sizeable) without having to write a vi that traverses the hierarchy and check the state of every vi.
The methods to retrieve this information already exist, they simply need their access changed from private to scripting or public. Unless of course they are private because they would blow up your computer, but somehow I suspect they are the same methods used by the error list.
I like this idea because it would allow someone to see all vis broken in their hierarchy (which can be sizeable) without having to write a vi that traverses the hierarchy and check the state of every vi.
There is already a way to do this - the top VIs in the error list are the ones which are broken and they are marked with a red X. This covers the common manual case (just in case you were talking about that).
Yes, but there's no need for that if all you want to do is see the actual broken VIs in your hierarchy, which was the text I quoted. Like I said, I was referring only to the manual case.
trying to revive this discussion.. is there a way to find out the error messages using scripting ? i would like the code to look through a couple of vis and let me know what exactly is the error in the vi. greatly appreciate the help!
