LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

'Select File Path' popup will block 'Open file' vi

Solved!
Go to solution

Thanks,it is a good idea.

 

To transfer data, I always use queue. For the log record, will user event be better?

0 Kudos
Message 21 of 27
(1,519 Views)

Queues are more easily for programming (just from my point of view). But events also OK.

 

Andrey.

Message 22 of 27
(1,518 Views)

"turbot" <x@no.email> wrote in message
news:1227534007395-813684@exchange.ni.com...
> Thanks?it is a good idea.&nbsp;To transfer data, I always use queue. For
the log record, will user event be better?

Events have a few advantages. I'm sure queues have some too, but I like
events.

One advantage is that you can send one event, and catch the events in
multiple event structures. In this case, the log.vi could store the message,
and the main mmi might display it. The only thing any loop has to do, is to
register to the user event.

The second advantage is that you can (actually, you have to) integrate the
event processing in your user inverface events. So you only have to make one
loop, that handles normal events, and the user events.

Another way to do the logging is to simply make a vi that opens, writes to,
and closes the vi. You would be supprised how well this works!

Regards,

Wiebe.


Message 23 of 27
(1,503 Views)

Hi, Wiebe,

 

You wrote: "One advantage is that you can send one event, and catch the events in multiple event structures."

Are you really sure that you will catch all events in multiple event structures?

Attached VI contained two events structures and one for loop, which fires 10001 Events.

Not all events obtained in both loops. At least for me. In additional after few runs this VI will crash.

Yes, I know that its not good to place multiple events structures on the same diagram, but this short test shows that something may be potentially wrong with events.

 

  

 

Andrey.

Message Edited by Andrey Dmitriev on 11-24-2008 06:55 PM
Download All
Message 24 of 27
(1,497 Views)

Thou shalt not split the Event Registration Refnum.

 

 Instead you should split the event refnum and register twice.

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
Message 25 of 27
(1,486 Views)
Solution
Accepted by topic author alex.
Ton, thanks for this remark!
Message 26 of 27
(1,469 Views)
I never said I use two event structures in one VI.

I start all my VI's dynamically, and each dynamically started VI has an
event structure. That works flawlesslly.

Regards,

Wiebe.


0 Kudos
Message 27 of 27
(1,455 Views)