LabVIEW
Wire value changes on output tunnel
Side note: This is a four year old thread that got bumped by a distracting post that is under discussion in several other places and does not really belong here too.
@*3d0g wrote:
Yep, I'm calling it a bug. My array should've been fine, but it wasn't.
Of course you can call it a bug.
The question is who's bug it is 😊.
As you post only part of your code (in the wrong thread as mentioned) it's hard to say...
DLLs that manipulate data messes up LabVIEW's internal data management it ways that you're basically on your own. That's no bug per se. It doesn't state anywhere that it should work or how it should behave. If your array lives in a IPES, make sure the input has 'modifier' turned on, because LV won't tread the data as changed by itself. For instance, running a VI twice with data that wasn't changed (by LabVIEW) can easily result in constants that return modified data from a previous run. LV will simply reuse the data, not being aware of it's data changes.
Search LabVIEW like a graph! 