LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Is there an easy way to check if a numeric button is pushed?

Solved!
Go to solution

Mo,

I see you like to argue so here it goes. 🙂

 

1. Repeating. Everything except the big loop is and addition to show the button functionality.

2. While loop is infinite in order to be able to play with the buttons as long as you like. Just hit the red stop button when you feel like.

3. Property node/reference  was made by the snippet.

4. When it comes to memory, your loop was infinite. Mine had allocated 6 elements. Wihtout allocating those 6 elements it does not work all, which tells me you did not run the code 😉

0 Kudos
Message 31 of 34
(843 Views)

@AndyN wrote:

Mo,

I see you like to argue so here it goes. 🙂

 

1. Repeating. Everything except the big loop is and addition to show the button functionality. Understood

2. While loop is infinite in order to be able to play with the buttons as long as you like. Just hit the red stop button when you feel like. As I said, I don't know your experience or intention.  Many users get on this forum and make mistakes like this. I was simply pointing it out in case you didn't know.  I for one would explain things to fellow forum members before submitting something so blatently obvious. And no, something so obvious would not be common sense as to your intention.  I can't read your mind.

3. Property node/reference  was made by the snippet.My apologizes, you said the reference was made by the snippet, which I assumed, but did not appear to address the property node.

4. When it comes to memory, your loop was infinite. Mine had allocated 6 elements. Wihtout allocating those 6 elements it does not work all, which tells me you did not run the code 😉Yes, I ran the code and it worked like I would expect it to.  Perhaps you were expecting a different result.  Mine populated 6 elements, and not infinite as you claim.  What do you mean by it "didn't work at all?"  What result did you get?  If you can give me the details, I will try and duplicate it.


 I am not being argumentative.  I was simply making a point and giving some friendly adivce regarding your code.  Lost in all this mess is a solution to your original post.  Do you have one?  I see no need to continue on this tangent.  It's non-productive.

-----------------------------------------------------------------------------------------
Reese, (former CLAD, future CLD)

Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home
Message 32 of 34
(840 Views)

Hey, 

It is all OK. I do appreciate your comments.

I just felt some of them were going a bit away from the main problem.

 

Yes, the array of Boolean clusters with the logic did the job for me.

And again, thanks for the whole discussion.

0 Kudos
Message 33 of 34
(832 Views)

@AndyN wrote:

Hey, 

It is all OK. I do appreciate your comments.

I just felt some of them were going a bit away from the main problem.

 



Many people read the posts here and as a general rule more experienced folks here like to correct basic flaws in posted code. Many of the people readin these threads are new to LabVIEW and don't really understand data flow or some of the ways LabVIEW works. Answers and advice posted here are not only intended for the OP of a thread but also those poeple who are reading it. Lots can be learned by reading the threads and everyone can benefit by advice on how to  improve code.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 34 of 34
(825 Views)