Why is this "Operation not valid for strict type definition instance"?

[X.]

This is sort of a follow-up to that message where I described what I think is a bug which does not allow using the "IndexVals" property of a Strict Typed Def array in "Write" mode (at least without jumping through a few hoops).

In short, if I take a reference to a Strict Typed Def array and use the "IndexVals" Property in "Write" mode in a SubVI (which I can access without gimmick, interestingly), this throws an error 1082, with the following Explanation:

LabVIEW: Operation not valid for strict type definition instance. Property Name: Index Values

I have searched for both the error code and the error message and found these threads:

http://forums.ni.com/t5/LabVIEW/Error-1082-when-setting-Strings-property-of-a-menu-ring-control/m-p/...

http://forums.ni.com/t5/LabVIEW/error-1082-with-active-cursor/m-p/146497

http://forums.ni.com/t5/LabVIEW/Why-does-a-strictly-Typed-Control-cause-error-1082/m-p/125418

It seems to have been diagnosed as a bug (but without a CAR) at least since 2004, but apparently this is still an issue in LV 2013 SP1 (which I tested it in).

Nothing about Strict Typed Def throwing an error with this property in the Help.

Time to kudo this idea... and fix this bug!

[WireWeaver]

Hi X,

I think Paul may have answered this question in the message this post is referencing. Part of the functionality of a strict type def is restricting what you can change. 

http://forums.ni.com/t5/LabVIEW/Array-Index-Values-Property-Read-Only/m-p/3112536#M892653

[X.]

I think Hoovahh in that thread has objected to that answer better than I could have.

Now, it is perfectly fine for NI to stand their ground but it doesn't make any of the things I have reported consistant for that reason.

[WireWeaver]

Hi X,

So we dug a little deeper into this and couldn't find a CAR filed for this specific issue. A new CAR was created (#512512) and R&D will investigate this further. 

You can monitor the list of known issues and bug fixes at links such as these:

https://www.ni.com/en/support/documentation/bugs/14/labview-2014-and-2014-sp1-known-issues.html

https://www.ni.com/en/support/documentation/bugs/14/labview-2014-bug-fixes.html

Thanks for bringing this to our attention!