events

[Nick_F]

Thank you very much Daniel, it works beautifuly.

I noticed you used a local variable to control the scale mapping loop, it is interesting. Can it be replaced with a value property of the control? I read that local variables make the application run much slower in some conditions.

I have a question about the tunnel between the charting loop and the scale mapping loop. Is that tunnel used by the application? Because I don't see a purpose to it. Yet, when I delete it, the application seems to run with some interruptions (not as smoothly as before, the data plotted on the chart seems to freeze for very short periods of time).

Regards,

Nick

[TCPlomp]

  On the contrary locals are much (100 times or more) faster than property nodes, only locals (and property nodes) can give you race conditions.

Ton

[dan_u]

Hi Nick

Ooops, I forgot to put a wait in the second loop where the local variable and Rerun are read out. Put a wait of at least 10ms, better 50ms, in that loop. Else it's one of these 100%-CPU-load-loops because it's not slowed down in any way.
The tunnel between the two loops isn't required. With the tunnel, the second loop will only start once the DAQ loop has finished. Else, the two loops will run in parallel. The sluggish behaviour was most probably because the second loop has no wait. The advantage (in my opinion) of the tunnel is this: if you click the rerun button while the DAQ loop still runs, it will stay pressed until the second loop starts. So you see it's not ready yet to read it out yet.
Or were you talking about the tunnel from the property node to the two loops? This is because "stop app" should be false before the loops start. Else the lower loop (especially without tunnels between the two loops in it) might stop immediately. So this would lead to one of these race conditions...
About the local variable: parallel programming is really easy with LabVIEW. But the two loops need a common stop condition if you want to stop the application. There are other ways of doing that, but the local var is the easiest.

Daniel

[nag123]

hi i am jabili . i want creat mouse double cilck event  on blank vi .when double cilck on the blank  front panel my sub vi should be open .but in event structure there is no mouse cilck event .plsese tell me how to do  that one

[RavensFan]

I just discovered this double click event myself elsewhere on the forums.

In the event for a particular control, choose the mouse down event.  There is a Mods element to the left hand side of the structure.  Choose double click out of the sub menu for that.  It returns a boolean as to whether the mouse down event was a double click or not.  It is also available for the Pane mouse down event.

Message Edited by Ravens Fan on 12-26-2007 06:03 PM

[pallen]

The Fourm search hits gold again!

Thanks Ravens Fan.  This is exactly what I was looking for this morning.  I knew there had to be an easy way of doing it.