How can I Assert that an input enum contains a particular item?

[DavidJSzwer]

I'll take a good look at that, thank you!

[Edit]  Yes, it seems to work very nicely - thank you very much!

[JÞB]

I THINK that you may have to pass a cluster of <reference to the enum type and enum value> into your vim and throw an error if the value string is not supported.

Or, I could be mistaken. I haven't played with the new vim pallet enough myself.  And it won't break the run arrow.

[Hooovahh]

---

@paul_cardinale wrote:

Here.  Made with LV 2019.  If you're using a later version, I recommend mass compiling it.

This is a very low risk XNode because it has no runtime functionality.

---

Yet another fantastic XNode, that solves a problem that couldn't be done any other way at least at edit time.  Do you have a page, or package, or link to where all of your XNodes are?

[paul_cardinale]

---

@Hooovahh wrote:

---

@paul_cardinale wrote:

Here.  Made with LV 2019.  If you're using a later version, I recommend mass compiling it.

This is a very low risk XNode because it has no runtime functionality.

---

Yet another fantastic XNode, that solves a problem that couldn't be done any other way at least at edit time.  Do you have a page, or package, or link to where all of your XNodes are?

---

Sorry, I don't.  I just cobble things together and throw them over the fence.

[Hooovahh]

---

@paul_cardinale wrote:

---

---

Sorry, I don't.  I just cobble things together and throw them over the fence.

---

No worries I do the same.

[paul_cardinale]

There's a mistake in "Verify Enum String\Support\Verify Enum String\GetHelp.vi".

It says "... to change label."

but is should say: "... to change the string."

[paul_cardinale]

---

@Hooovahh wrote:

---

@paul_cardinale wrote:

Here.  Made with LV 2019.  If you're using a later version, I recommend mass compiling it.

This is a very low risk XNode because it has no runtime functionality.

---

Yet another fantastic XNode, that solves a problem that couldn't be done any other way at least at edit time.  Do you have a page, or package, or link to where all of your XNodes are?

---

Just dug through my files.  Here's a list of the one's that are suitable for sharing:

Array Size.xnode
Asynchronous Call.xnode
BronxCheer.xnode (silly)
Call By Ref in Other Context.xnode
Compare to Constant.xnode
Convert String to Almost Anything.xnode
Decoration Reference.xnode
Edit Image Constant.xnode (zero risk)
Icon Constant.xnode
Index and Unbundle.xnode
LVObject MethodSelector.xnode (zero risk)
Numeric with Named Bits.xnode
Place Column in 2D Array.xnode
Relabel and Default Value.xnode
Slippery.xnode (silly)
Sort Array of Clusters by Specific Cluster Element.xnode
String Arithmetic.xnode
Sync and Stall Data Flow.xnode
Unbundle Refs By Name.xnode
Unrestricted Invoke Node.xnode
Verify Enum String.xnode (low risk)
XControl Direction Enforcement.xnode

XControl Indicator Init.xnode

[paul_cardinale]

Here.

And now for the fun part: Who wants to double check that I didn't break anything when I repackaged them?