LabVIEW
Strange array of ctl behaviour
Solved!
@Quiztus2 wrote:
This makes hardly sense.
Yes it does. I cannot look at your code because the version is newer than what I have, but your diagram picture certainly raises a lot of eyebrows.
- Indexing out an element that does not exist gives you the default value for the datatype, not the default value for the element. A default value is a property of the terminal (control or indicator), not of the data in the wire. If would be really confusing to return real-looking data when indexing out of bounds.
- Why do you read from a local variable instead of the array terminal?
- What's the purpose of the error wire?
- Why do you need a greedy loop that cannot be stopped?
- You can easily add a tiny little bit of code that returns something specific if you try to get an element that does not exists. Instead of data, you should return an error of course. You can easily make the array have a default values where the size is not zero.
@JÞB wrote:
Get rid of the local. You don't need it the terminal is right there and unwired.
Get some type of timing in that loop and a stop condition! If you want the vi to respond to user input....use a value change event case.
The control is not behaving strangely, the programmer is!
The more experience you have, the more likely that what you want the program to do and what you tell it to do will converge. Hopefully.
On a side note, your question does have some validity!
Have a look at my 10 year old idea and its comments here. 😄
