BreakPoint
Do you write or draw a LabVIEW Program?
Solved!
@TAP_ wrote:
I was writing documentation for a customer, It was a development plan for adding additional functionality to already "Drawn LabVIEW code". I changed it because I through it was unprofessional.
"Existing LabVIEW code" is what i would have written. Code is code, whether assembler, C# or G. You dont program HTML/XML however, as some say, but format the information.
/Y
@NIquist wrote:
I've made a decision in this important matter that TAP has so graciously brought to our attention. From this point on and until eternity ends...
I will CONTRIVE my VIs. So let it be written (typed or drawn), so let it be done (run or executed)!
Oh yeah? Well, I use MAGIC! Thus, I poof! my VIs. So there! 
@smercurio_fc wrote:
@NIquist wrote:
I've made a decision in this important matter that TAP has so graciously brought to our attention. From this point on and until eternity ends...
I will CONTRIVE my VIs. So let it be written (typed or drawn), so let it be done (run or executed)!
Oh yeah? Well, I use MAGIC! Thus, I poof! my VIs. So there!
Do you make sound effects to go with the poofing?
@Hornless.Rhino wrote:
Do you make sound effects to go with the poofing?
I thought that might have been overdoing it. 
@smercurio_fc wrote:
@Hornless.Rhino wrote:
Do you make sound effects to go with the poofing?
I thought that might have been overdoing it.
Not really.
And- For the final goal---TAP__ Severio just whipped up a quick example on a whim. LabVIEW users of all achievement levels can understand the simple example.
Duplicate it in the language of your choice.
Steve C.-- Could you jing that demo- TAP__ might not be able to see what it does?
