10-19-2017 05:04 PM
This is what happened:
I'm an avid user of defining custom type definitions and I have never seen this behavior. I haven't been able to recreate this.
Does anyone can help me to clarify what may have happened?
Thank you!
10-20-2017 06:02 AM - edited 10-20-2017 06:05 AM
Sounds a lot like this:
https://forums.ni.com/t5/LabVIEW/strict-type-def-data-blown-out-when-updated/td-p/2197480 If it is, it's by annoying but by design.
Or this:
https://lavag.org/topic/16728-enums-losing-their-values-again/
10-20-2017 10:14 AM
Thank you for those references. I learned something that I'm not sure why was never clear to me after all these years of use.
It is annoying and frustrating.