Continuously update table

[niedk]

I think thoult already answered my question for the most part. I know that I can't connect a single data point to an array sink, my problem was trying to figure out how to use shift registers to build the array.

What I'm trying to do is have multiple testing options that access the same indicator on the front panel. I was simply trying to figure out a way that I could pass data out of these loops so that I could update the indicator regardless of the test that was run.

[altenbach]

That shift register only builds you a 1D array and having the building of the table outside any loops makes it update only once. Lots of details are missing.

[niedk]

It seems to continuously update when using a local variable outside the loop, at least for the numeric indicator. What is the best way to make my data from my sample program into a 2D array? Could I use the shift registers in conjuction with a Reshape array function?

[altenbach]

Why does it have to be a table? You could use a plain array 1D indicator instead, right?

Do you want to build a single column or a single row in the table?

[altenbach · Accepted solution]

Here is a quick draft.

Of course you might want to wire directly to the table terminal inside the loop and read it from a local varaible elsewhere instead. It really depends on the situation, which is currently not clear. Can you explain why you need all this? Maybe there is a much more elegant solution.

[niedk]

It doesn't need to be a table for this case I guess, I was just using that because it was a front panel indicator that would display multiple data points? What 1D array indicator are you referring to?

[niedk]

Ok thanks! So for local variables you dont need to wire a read function of the local variable into the table itself? It automatically sends the data to the table by itself?

[altenbach]

A local variable just points to the value of an user interface object, it is not something separate. You really need to start with a few turorials!

(Of course local varaibles can lead to race conditions and force additionl data copies in memory, but that's a seperate discussion. Local variables blur the distinction between control and indicator, because they allow to write to a control and read from an indicator. This is useful to ui programming, e.g. to programmatically modify user controls.)