Error Ring accepting Enum

[wiebe@CARYA]

It would be nice if the Error Ring would accept enums.

So the Error Ring does not accept an enum (A). Format Into String does (B). So now we need the extra step of putting a Format Into String before the Error Ring (C).

This would be more convenient in for instance state machines (D) or functional globals with a function enum.

While on it %s on FIS also accepts Booleans. Nice to have the error ring accept them as well, just for completeness.

[wiebe@CARYA]

Reconsidering posting this idea was triggered by this idea: Make text search look inside error ring constants.

[joerg.hampel]

+1 for this.

I understand from Stephen's comment on the other thread that it might not be as easy as it seems to make the error ring behave just like other prims do. But as my dad used to say, I can wish for everything 😉

[wiebe@CARYA]

I think this one is easier to implement. Just some XNode magic, versus completely refactoring the search algorithm.

How about this one: Error Ring Error in?

[AristosQueue (NI)]

Done. If it survives testing, it'll be in LV 2019.

Some things are easy.

[joerg.hampel]

Where's the kudos button for comments to ideas!?

[wiebe@CARYA]

That's great! Thanks.

[Darren]

Available in LabVIEW 2019 and later. A string or numeric parameter terminal on the Error Ring can now accept an enum data type.

[wiebe@CARYA]