07-25-2008 12:36 AM
Padmavathi.B wrote:
I have purposefully placed two buttons in single event i.e start, stop.I have clearly ensured that the delay is not with these two buttons in the event structure.
07-25-2008 01:00 AM
I know.
But i have written the code a/c to my application .
07-25-2008 01:11 AM
Sorry, I don't understand. What application? Why Air conditioning?
Padmavathi.B wrote:
But i have written the code a/c to my application
07-25-2008 08:25 AM
I think a/c means according in this context.. or maybe I'm wrong 😉
back to serious mode
Now what is the logic behind having the same event handle both the Start & Stop?????
Think about it for a moment. It is absolutely flawed. Sorry to sound harsh, but start & stop are at the completely opposite ends of the spectrum, so why would you want to combine them? In any case, it will never work.
To learn more about LabVIEW, I suggest you try looking at some of these tutorials.
You might also try having a look at these video tutorials..
R
07-28-2008 12:23 AM
Hi,
Start and Stop buttons in a single event structure will run with out any problem. If you want to know about this just run my "Query.vi".
But my problem is due to "DAQmx Clear Task".vi but not with the event structure.
Your are completely deviating from what i am asking.
Ok any way leave the problem.
I will solve on my own.
Thanks
07-28-2008 01:53 AM
07-28-2008 06:13 AM
Padmavathi.B wrote:
Start and Stop buttons in a single event structure will run with out any problem.
OK. sorry to try to help you.
Padmavathi.B wrote:
Your are completely deviating from what i am asking. Ok any way leave the problem. I will solve on my own.
07-28-2008 11:34 AM
JoeLabView wrote:
Padmavathi.B wrote:
Start and Stop buttons in a single event structure will run with out any problem.
Glad to read that... surprised... (no... astonished)
What happens in (3) is completely unecessary, and if you would just remove the stop trigger from the event case, you could also remove the case structure, because it is no longer needed. Only (1) is useful coding! The example displays a fundamental misunderstanding of the event structure.
What we have here is a NOOP that qualifies as pure Rube Goldberg code.
The code is so full of weed that ist is difficult to tell the necessary stuff from all the fluff, making debugging (such as solving your problem) nearly impossible.