LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Colum or Row choosing in For Loops

Hi folks,

I'm just wondering why/how LabVIEW choosed to make a Row instead of a Column while indexing in a For Loop.

 

If you make a 2D array, and your first indexing data array is actually something you want to represent in a column, you have to transpose your array, is it normal, am I missing something?

 

I don't have actual issue with that, but I was just curious to understand if there is some philosophical explanation to that choice.

 

I don't propose any change to LV, I think it's enough easy to transpose the array, but I was just a little curious about this fact.

 

Thanks!

 

 

forloops.PNG

 

0 Kudos
Message 1 of 2
(1,957 Views)

Because the row is the lowest level index.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 2 of 2
(1,918 Views)