Block diagram for multiple text boxes

[dan.laks]

Thanks RavensFan.  So I would wire the front panel button to the top input connector.  But what would I wire to the other input connector?

[dan.laks]

Aalenox,

Actually, I do have other stuff in the main VI, although I could easily incorporate your approach into what I have now.  Ideally, I'd like to use a subVI if only because I think it would be useful for future projects.

Thank you, though, for taking the time to put together that example.  I didn't know you could combine references into an array like that.

[Aalenox]

---

@dan.laks wrote:

  I didn't know you could combine references into an array like that.

---

As a general rule, if something has a wire out - you can toss it in to an array 🙂

[dan.laks]

RavensFan,

Oh, I think I get it. The two inputs are the button itself and a reference to the button.  Is that correct?

[Aalenox]

Read this:

http://www.ni.com/white-paper/3159/en

[RavensFan]

---

@dan.laks wrote:

RavensFan,

Oh, I think I get it. The two inputs are the button itself and a reference to the button.  Is that correct?

---

Yes.  The reference on the button so that the subVI knows what control to work with for the property nodes.  I also set it to wire up the boolean directly to pass in the value.  Your VI had a value property node, which could have worked, but because of the latching action of the boolean, the data type for value was variant rather than a boolean.  So I figured it would be easier to just pass in the value rather than dealing with a conversion of the variant data type.

[dan.laks]

Ah, I was wondering about the variant data type.  I didn't think it had to do with the type of button (latching vs non-latching).  Thanks for the explanation.