Stop printing error controls and indicators in documentation

[Richard_Ha]

Is there a way of stopping the error controls and indicators from printing out in the documentation, whilst still printing out other controls and indicators?

I would like to have the information and captions printed out for my control and indicators (as it's very useful information), but the standard error in and error out on all of my SubVI's take up an entire page. As they are standard controls and indicators it seems a bit of a waste to print an entire page explaining the error cluster for each and every SubVI.

[BillMe]

When printing the VI documentation, I don't see any way to exclude the error clusters.

[Freelance_LV]

I am not sure if this would be a solution. however, i was planning to suggest to try hiding the front panel controls and indicators which you do not want to be seen on the report.

i have not tried this before, but just a suggestion

[Richard_Ha]

Even if they are hidden they still appear on the documentation when it is printed out.

[Freelance_LV]

hmm.. thats bad!

i am sorry but cannot think of any other options.

[Richard_Ha]

Submitted it to the idea exchange.

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Prevent-Error-Control-and-Indicators-descriptions-prin...

[LaThoS]

Hi Richard,

The way that LabVIEW prints documentation is via an invoke node called 'Print', which is called on every VI and control reference. If you really want to omit the error details, then you can write a VI to iterate through and generate the HTML/RTF manually. In fact one of our Applications Engineering Specialists wrote a documentation generator as part of his final year project.

Alternatively, could you print as HTML and then edit the HTML to remove the offending items? Then maybe convert to another format if required.

Kind regards,

Laurence

[Richard_Ha]

I think the way I will have to do it is to print to HTML and then just remove the bits I don't want with a script.

Just thought it would be nice for a SubVI to do this automatically, possibly as a user definable option.