LabVIEW
How to edit the element value of the 2d array of string indicator While Vi is in run condition.
Solved!
Please use "save for previous" before attaching. Many users here cannot open VIs saved in LabVIEW 2021.
Hi guru,
simple answer: when you (or the user) want to change FP element data then you need to use a control.
Indicators only show data (data sink), they aren't inputs (data sources)!
Why do you need so many references and property nodes to access array data?
What a mess! You have not said what you want to edit at runtime. I assume it is "table data". Right?
Tell us exactly how you use the program, what you then want to edit at runtime, and what you expect to see afterwards.
I think you should start over with the basic LabVIEW tutorials, because most of your code is just plain Rube Goldberg (example)! Once you are more familiar with the basic concepts of dataflow, things will become more clear.
- All your buttons should be latch action and their terminal belongs into their respective event. No need for local variables or inner sequences.
- Why are there hidden indicators with no functionality (e.g. Heart rate 2).
- Why in the world would you transfer the graph data to a table using "export to clipboard...clipboard read...parsing...", if you could just process the graph data directly?
- If you would use a table indicator, you could just write the table headers. No need for that pile of terminals.
- What exactly is the point of a FOR loop with one iteration?
- Why are front panel and diagram maximized to the screen? Nobody wants to stare at huge whitespace with no information.
- Why would you need to compose the same data2 array in two different places? That will make maintenance a nightmare because if you ever want to change something, you need to make identical changes in multiple places.
- The json path terminal belongs inside the event because it gets read right away, so if you change it and the execute the up button, it will operate on a stale path.
- Please give all terminals reasonable names. "Up button" and "Up button 2" are not reasonable. You should also spellcheck your boolean texts.
- All data that is needed in multiple event frames should be held in shift registers.
Compare these following two code segments:
Why would you need to reset to default if you are writing new data anyway?
(Note that if you have array diagram constants containing data, you should always make the container large enough to immediately see what the array size is. for larger arrays, just show the scrollbars instead.)
