push button problem

[thentangler]

Hello again guys..

Just wanted to update about my push button problem.

I final;ly found out that it is a Labview glitch. Like I mentioned it would work most of the times, but then once in a while it would get stuck in the pressed position. I found out that if I right click it, it would get un-pressed even when the program has finished running.

Weird LOL

But thanks for all the suggestions guys, I know I should change the architecture to make it more efficient. And I will, once i get more time and become more well-versed in Labview 

🙂 

[GregFreeman]

---

@thentangler wrote:

Hello again guys..

Just wanted to update about my push button problem.

I final;ly found out that it is a Labview glitch. Like I mentioned it would work most of the times, but then once in a while it would get stuck in the pressed position. I found out that if I right click it, it would get un-pressed even when the program has finished running.

Weird LOL

But thanks for all the suggestions guys, I know I should change the architecture to make it more efficient. And I will, once i get more time and become more well-versed in Labview 

🙂 

---

Yeah, I don't think that's a LabVIEW glitch; it's poor programming practices. Have you tried anything people suggested?

[thentangler]

Not yet,

But I have this problem with any labview program. Not just mine. Even with example vi's, and vi's i download from the web.

[RavensFan]

Then I would suspect your mouse.

Have you tried another computer?

[WNM]

What had been a well-behaved set of code to jog a stepper motor Fwd/Rev developed this same button problem after I added a subVI to also readout an encoder while the motor moved. It turns out that the encoder VI (copied from another project) was setup to "open front panel when called and close when finished" and I did not notice that it was doing the opening/closing thing off to the side as I jogged the motor. It would seem that the VI opening/closing thing was what fouled up my "switch while pressed" jog buttons because when I finally did notice the encoder VI's behavior and stopped it form occurring, my jog buttons went back to behaving normally.  FWIW, this is old but tried and trusted v7.1.1 code. Later versions of LV may not exhibit this behavior.