copy/paste "Error list" Items with errors as plain text ?

[jbeale1]

When I attempt to run a Labview project main.vi I get a long "Error list" window, listing many .vi files within the .lvproj as "Items with errors". I would like to get this listing as a plain text file for documentation purposes (another developer checked this code in, and it is supposed to be working).  However the small window cannot be resized very much and it is not a plain text field that I can copy and paste in the normal Windows way. Is there a way to export these errors as plain text?

[GuenterMueller]

I see no standard way in LabVIEW to export this list to a plain text file.
On the other hand: If I was passed a that long text file I would prefer to visit the originator than investigating that file. How about starting a remote session to the developer who checked the code in? There is a good chance that he just missed to check in a few files ...

[HizNI]

Have you tried connecting your error wires and using a simple error handler.vi at the end of your program? What version of LabVIEW are you using. If all else fails, you could take a screenshot of the error. 

[jbeale1]

Thanks for the responses. I'm using Labview 2014 SP1 Version 14.0.1 (32 bit) on Windows 7.

Certainly I do need to talk with the other guy but he won't be back for some weeks.  The errors I have cause a "broken arrow" condition so the program does not even start. Does an error handler at the end help me in that case?  Yes I can do a screen shot, but there are so many errors it would take about 5 screen shots to scroll through the (fairly small, non-resizeable) dialog box and capture them all.  

I was hoping for an easy way to capture this,  but now my guess is that LabView was just not intended to work that way.  I'm more used to other programming environments, where errors were always available in plain text format.

[tst]

I'm pretty sure that there's nothing in the API to allow this, and the window itself is built in C. One option which might work is using the tools in the Windows API to find the window, find the relevant control in the window and get its text, but I'm not familiar enough with that part of the Win32 API to give more details. A program like Spy++ or APISpy might give you some more info on which controls make up the window.

Another thing which might help, if you're not aware, is that LV shows the VIs which are actually broken at the top of the list with a red X. All of the others will stop being broken once those are fixed and often a very long list is there just because you have a few broken VIs which many VIs use.

[GuenterMueller]

---

@jbeale1 wrote:
[...]

I was hoping for an easy way to capture this,  but now my guess is that LabView was just not intended to work that way.  I'm more used to other programming environments, where errors were always available in plain text format.

---

My guess: Your project depends on drivers and/or toolkits that do not come with the LabVIEW installer.
Example: If your project performs data acquisition and you do not have DAQmx installed, this will result in broken VIs in the project - just as you described.
It might be helpful if you would post a couple of errors reported in the Error list window.

[HizNI]

Simple error handler will not help if you have a broken run arrow. If there is anything under the Details section of the error list, I am able to highlight it and ctrl+c to copy it then paste it into a document. Would having the Details of the error help?