Offer a Positive Logic Alternative

[JackDunaway]

As we look at the Comparison Palette, there are three functions that offer negative logic, but fail to offer the positive logic alternative:

I commonly find myself placing a Boolean "not" right after these functions (e.g., if I want to know if there are elements in an array I must test if it is "not not empty", or if I want to know if a ref is valid I must test if it is "not not valid". Take a look at my other idea which illustrates not not logic.).

I have two proposed solutions: 1. offer a single function that has an "Invert?" option on the output, or 2. offer both the positive and negative logic primitives on the palette.

Message Edited by Laura F. on 11-16-2009 08:51 AM

[jdunham]

Sorry to be late to the party, but I have to agree.  I use an inverted form of these functions much more often then the plain version.

I find it's much easier to maintain code if the TRUE case of a case structure is the one with the interesting stuff inside, and usually when data checked by these functions is empty or invalid, there's nothing to do downstream so that should be the FALSE case.

[dnoble79]

I agree, I would like to see inversion circles added to all comparison functions, potentially combining Equal and Not Equal into a single Equal function with optional inverted output and phasing out Not Equal. The same goes for the other functions.

An optional inverted input could also be added to the Select function to make BD nicer with less crossed wires.

[TomOrr0W]

Looking at the comments on this idea, I ended up searching invert, negate, bubble, and circle (skipping anything that was already marked duplicate).  I figured I might as well link the related ideas.

Strongly Related:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Negate-option-on-Comparison-functions/idc-p/3793254

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Invert-Option-in-all-Boolean-Terminals/idi-p/1281058

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Array-String-not-empty-function/idi-p/3163821

Related:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Shortcut-to-Invert-Input-Output-in-Compound-Arithmeti...

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Correct-the-quot-not-quot-symbol-by-removing-the-inve...

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Automatically-invert-compound-arithmetic-inputs-when-...

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/General-Comparison-Operator-as-an-Express-VI/idi-p/12...

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Simplifying-Boolean-expressions/idi-p/1890963

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Invert-signal-going-into-a-select-VI/idi-p/2224232

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Negate-input-on-boolean-functions/idi-p/1084159

A couple people (not in this idea) mentioned making inversion bubbles more visible:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Enlarge-the-Invert-Circles/idi-p/1023748

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Replace-the-Invert-Circles-in-Compound-Arithmetic-Nod...

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Compound-Arithmetic-with-inverted-input-should-be-eas...

[Petru_Tarabuta]

+1. "I commonly find myself placing a Boolean "not" right after these functions" (quoted from original post) and "I use an inverted form of these functions much more often then the plain version." (quoted from jdunham comment above) - This is 100% my experience too.