VI Analyzer spell check skips VI Description

[paulmw]

I can't seem to get the VI Analyzer to catch spelling errors in the VI Description.

Is this functionality broken or unavailable?

Attached is an example VI that when Analyzed under default Analyzer setting won't catch the obvious spelling errors in the description.

[muks]

See here

[paulmw]

Hey muks,

Were you able to confirm that the VI Analyzer won't spell check the VI Description?

[Darren · Accepted solution]

Hi Paul,

Before you perform the analysis, make sure both "VI Information" and "Non-Visible Text" are selected in the Spell Check test configuration:

[muks]

I have used VI Analyzer Toolkit to spell checkblock diagrams and front panels only.

[paulmw]

I didn't have the "Non-Visible Text" checked.  I am a bit confused as to what Non-Visible Text is and also why it wouldn't get automatically checked if VI Information is checked.  Is there such a thing as "Visible Text" in "VI Information"?

[Darren]

---

@paulmw wrote:

I didn't have the "Non-Visible Text" checked.  I am a bit confused as to what Non-Visible Text is and also why it wouldn't get automatically checked if VI Information is checked.  Is there such a thing as "Visible Text" in "VI Information"?

---

The way the test currently works, the "Visible Text" in VI Information is the VI Name on disk and the VI Title.  When you check "Non-Visible Text", that includes the VI Description and the VI History.

[paulmw]

---

Darren wrote:

The way the test currently works, the "Visible Text" in VI Information is the VI Name on disk and the VI Title.  When you check "Non-Visible Text", that includes the VI Description and the VI History.

---

Darren,

This makes perfect sense now, but where could I have found this information on my own.

Thanks,

Paul

[Darren]

I had to look in the code to verify the behavior, so clearly we need to document it better.  I'm thinking the easiest place would be the context help of the checkboxes in the test configuration.  Would that be a suitable location in your opinion?

[paulmw]

Yep - Context Help was where I was looking for it first - then the LabVIEW help - then the user manual from the web...