Suppress output configuration warnings unless they are releveant

[altenbach]

When converting a new VI back to LabVIEW 8.0, we get tons of warnings in the form:

The object "Multiply" does not support output configuration in the previous version.
The object "Multiply" does not support output configuration in the previous version.
The object "Subtract" does not support output configuration in the previous version.
The object "Add" does not support output configuration in the previous version.
The object "Multiply" does not support output configuration in the previous version.
The object "Divide" does not support output configuration in the previous version.
The object "Subtract" does not support output configuration in the previous version.
The object "Divide" does not support output configuration in the previous version.
The object "Divide" does not support output configuration in the previous version.

...

(see also this recent discussion, especially my comment).

The idea is that these warnings should only occur for function instances where the output was actually configured to be different from the default.

The current problem is similar to the problem with the boy who cried wolf, finding important warnings in a huge pile of useless warnings is like finding a non-magnetic, non-metallic, non-fluorescent needle in a haystack, and it is easily possible to miss something that is actually important.

[Yamaeda]

I concur!

[JÞB]

The information that the warnings ATTEMPTED to communicate is well beyond the ability of the novice LabVIEW user to interperate.  DO NOT kill the warnings~~ reformat them in such a way as to make them user FRIENDLY.  For instance- provide a "detailed info" selection that will explain the functional differances between the LabVIEW primitave's functions.  (I'll bet Dollars to doughnuts that these "change discriptions" could be adapted from memos that are on file as part of NI's internal release process)

[altenbach]

> DO NOT kill the warnings

There is nothing wrong with relevant warnings, but that's not what this is about.

A warning should only appear if the code actually uses a feature that is not available in the older target version. For example let's look at the case of the "in place element" structure, we should not get a warning that it is not available in 8.0 unless the program actually contains that structure.

Same here! If, and only if, the code contains specifically configured outputs, we should get the warning, otherwise not. 🙂

In this particular quoted case, the user got 150 such irrelevant warnings. However, there is nothing to "fix" and nothing that can be done. The code is fully functional in the lower version, without any loss of existing functionality. No warnings should be generated at all here.