Property node of a control inside of cluster inside an array

[aputman]

---

@Ben wrote:

Re: That path

See here

---

$35 for that thing.  LOL 

[Ben]

---

@aputman wrote:

---

@Ben wrote:

Re: That path

See here

---

$35 for that thing.  LOL 

---

Thanks for pointing out I included the wrong link.

The correct link should be this one.

Re:$35

I think this may be only the second time I have been asked to include filler modules. But the customer wants them so I do what they ask.

Ben

[altenbach]

---

@aputman wrote:

---

@Ben wrote:

Re: That path

See here

---

$35 for that thing.  LOL 

---

I am sure the shipping box has that big red warning sticker about sensitive electronic equipment. 😄

(I remember back in the mid nineties receiving a plain NI DAQ cable with that sticker on the box :D)

[aputman]

---

@Ben wrote: I do not think the documentation staff ever considered what you were trying as being possible let alone actually trying to do it.

Re: That path

See here

---

Ben's comment about the documentation staff was pretty funny, especially when you look at the original PDF document that he linked about the filler module.  It's a two-pager with the "module" weight and a page for contacting support, if needed. 

I wasn't quite sure what it had to do with the topic at hand but I knew Ben had a reason.  Turns out I was wrong. 

[MrJackHamilton]

Altenbach,

I 100% agree!. There seems to be some MIS-perception of late in LabVIEW code I'm seeing newbie's write that use the Front panel controls and indicators as repositories of variables...and thus when trying to perform operations on the 'variables' they are using property nodes and references, instead of manipulating the data in/on the diagram.

This must be some residual from python or something...it's mind-blowing to a seaoned LV developer...

Regards

Jack Hamilton

[Mancho00]

---

@MrJackHamilton wrote:

Altenbach,

I 100% agree!. There seems to be some MIS-perception of late in LabVIEW code I'm seeing newbie's write that use the Front panel controls and indicators as repositories of variables...and thus when trying to perform operations on the 'variables' they are using property nodes and references, instead of manipulating the data in/on the diagram.

This must be some residual from python or something...it's mind-blowing to a seaoned LV developer...

Regards

Jack Hamilton

---

It's not all that far-fetched from a 'classical' programming perspective.  If someone new to LabVIEW searches for information on 'variables' as they would be referred to in most other languages, they will find local variables, which of course are tied to front panel controls/indicators.  They could make the assumption this is how to store data in LabVIEW. If they want to access the (possibly changing) values of those variables in a subVI, then it makes sense to pass a reference to the control/indicator.

I'll admit I thought the same when I started using LabVIEW.  I think NI did people a disservice in some of their nomenclature.