dynamic mechanical action button

[phyrex_black]

Hi! Firstly I want to apologize for my english because is not very well! Well, I recomend a Shift Register of Type Boolean to avoid use Local Variables and even you can try to use Channel Wires to pass data from While Loop to another and another way maybe you try to use Property Node (Value) and put in parallel to send data for the VI

[Bob_Schor]

Hello, @phyrex_black.  Never mind your English, you are commenting on a post that dates from 2010!  I am the last Poster in that series, and I honestly don't remember how I "solved" my problem, but this was my first LabVIEW project, and I was attempting to completely rewrite a large, completely-undocumented LabVIEW Real-Time routine with multiple actuators and stimulators, and multiple channels of A/D and D/A inputs and outputs.

I ended up with back-to-back (Host and Remote) Queues State Machines, with Network Streams (4 of them, if memory serves) communicating between Host and Remote.  Worked wonderfully, more than twice as fast as the original code, and didn't crash in the middle of a data session.

I don't remember how I "solved" this problem, but I'm pretty sure I was using as few Local Variables as possible.

Bob Schor

[JÞB]

---

@Bob_Schor wrote:

Hello, @phyrex_black.  Never mind your English, you are commenting on a post that dates from 2010!  I am the last Poster in that series, and I honestly don't remember how I "solved" my problem, but this was my first LabVIEW project, and I was attempting to completely rewrite a large, completely-undocumented LabVIEW Real-Time routine with multiple actuators and stimulators, and multiple channels of A/D and D/A inputs and outputs.

I ended up with back-to-back (Host and Remote) Queues State Machines, with Network Streams (4 of them, if memory serves) communicating between Host and Remote.  Worked wonderfully, more than twice as fast as the original code, and didn't crash in the middle of a data session.

I don't remember how I "solved" this problem, but I'm pretty sure I was using as few Local Variables as possible.

Bob Schor

---

Don't remember or, wish you knew then what you know now?

[altenbach]

---

@phyrex_black wrote:

Well, I recomend a Shift Register of Type Boolean to avoid use Local Variables 

---

Please do not respond to decade+ old thread with some fuzzy descriptions using big words.

Since we need to sometimes programmatically change the value of a control here, the local variable IS the obvious solution. 

[paul_a_cardinale]

I hate user interfaces wherein controls change their behavior on the fly.

[altenbach]

Well, they can be on the fly without ever changing their behavior. 😄

 

[paul_a_cardinale]

---

@altenbach wrote:

Well, they can be on the fly without ever changing their behavior. 😄

 

---

I only know how to put controls on a front panel.  I don't know how to put them on a fly (and I'm pretty sure I don't want to learn).

[NIquist]

I can't believe a Knight of NI is promoting "buggy" code! 😮