Array Element.Disabled

[nyc_(is_out_of_here)]

I have an existing VI where the original programmer has a 2D array of booleans.

He sets the Array Disabled property to Disabled and Grayed Out.

He is also setting the Array Element.Disabled property to Disabled and Grayed Out.

I am not understanding why it is also necessary to do the latter.

[crossrulz]

Yeah, my quick test shows there is no point in also setting the disabled property of the control in the array.

[JÞB]

The only reason I can think of to write the properties seperatly is to possibly be able to scroll through the array and view (but not change) data with the scroll bars "Looking" Normal.  If it isn't a purely UX requirement I would question the developer as to why the code was missing that comment.

[nyc_(is_out_of_here)]

The programmer is gone.

[JÞB]

---

@nyc_(is_out_of_here) wrote:

The programmer is gone.

---

Well, Now you know exactly who to blame!  Next, you need to guess if that was a real requirement or if the developer needed another cup of coffee that morning. Then add the BD Comment stating your guess.

[nyc_(is_out_of_here)]

---

@JÞB wrote:

---

@nyc_(is_out_of_here) wrote:

The programmer is gone.

---

Well, Now you know exactly who to blame!  Next, you need to guess if that was a real requirement or if the developer needed another cup of coffee that morning. Then add the BD Comment stating your guess.

---

He had LabVIEW Core 1, Core 2, and Core 3 training and yet never heard of using auto-indexing with FOR loops.