LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Obtaining data from queue and writing to file

Hi jm,

 

there is only one condition where I want them to stop

Ok, then why do you have multiple buttons when all you need is "one condition"?

That's what I meant with my remark…

 

other than it looks messy.

Messy code is always error-prone. In every programming language, not just LabVIEW!

And you are the one who has problems with its code…

 

How far have you come with cleaning up your VI(s)?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 11 of 13
(669 Views)

"""

Ok, then why do you have multiple buttons when all you need is "one condition"?

That's what I meant with my remark…

"""

Individual control over each instrument (admittedly there were more than this required as well). It was useful whilst I grew the program to handle multiple instruments. I have now removed the extras and they are all linked to a single stop button. 

 

"""

Messy code is always error-prone. In every programming language, not just LabVIEW!

And you are the one who has problems with its code…

"""

Point taken.

 

"""

How far have you come with cleaning up your VI(s)?

"""

There is still work to do, but I know how to do it. I have fixed the issues I had in my original post, but then other things required my attention.

0 Kudos
Message 12 of 13
(658 Views)

Imagine text code with random indents.  The compiler doesn't care, but if a fellow programmer wanted to strangle you for it, I would look the other way while it was happening.

 

This is what messy code is analogous to.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 13 of 13
(647 Views)