Handing over (const) EnumArr as SubSeq-Parameter will cause a Type Conflict

[AdrianBiehler]

"Expected Array of (in my case) NumericEnum, found Array of Containers.

This value will cause a run-time error."

Thats the quote i get when trying to use a simple created Enum as parameter for a SubSequence, but as an array and written as a constant.

See the following:

Sure I could create a variable somewhere with exactly the desired type, hand it over and it will work out. But thats not what I want.

Someone has a workaround with the TestStand API?? Other solution might be that I will handover the indicies of the different enum values i would like to have. But than I wouldn't need an enum in the first place.

Kind regards,
Adrian

[stefanha]

This honestly looks like a bug to me.

It looks like the Engine checks the type of the array element, sees that the type of Enums is container, stops checking there and detects and reports the conflict.

Instead of realizing that the subelement NumericEnum inside the Enums container is referenced, which has the correct type NumericEnum.

Unfortunately this is not just an indication issue of the Sequence Editor, as it is for other issues that report an error but can be executed anyways.

I hope someone with deeper insight responds to this thread.

Stefan