Pit falls of using an event structure inside of a SubVI

[altenbach]

That's exactly the problem with the current rating system. Low ratings often have nothing to do with the topic, but are often triggered by "spur of the moment" animosity or even misunderstandings.

Once somebody is know to dole out low ratings, nobody will answer him anymore, really hurting the usefulness of the forum. It always has a chilling effect and does not promote the free exchange of ideas.

See also e.g:

http://forums.ni.com/ni/board/message?board.id=130&view=by_date_ascending&message.id=3460#M3460

http://forums.ni.com/ni/board/message?board.id=130&view=by_date_ascending&message.id=3321#M3321

I only give or no rating. everything else is useless ... 🙂

[RJay]

---

Nickerbocker wrote:
But what does using a queue in this situation buy me over using local variables.  If I'm not concerned about FIFO and just want to read the current value of the indicator/control then NI has created this wonderful ability to create a local variable of the indicator/control.  I don't think NI put the ability in LabVIEW in order to trick me.

I appreciate the help that these forums provide me with and appreciate your input.  I just want to know what *your* reason to use a queue in this situation is over local variables.  I have read the style guides template but I do not believe taking more courses is going to make me a better programmer.  I prefer a good book to read over an instructure that tells me a lot of what I already know.  I know how to use queues and use them when appropriate.


Message Edited by Nickerbocker on 06-17-2008 02:57 PM

---

You should have explained the constraints for your specific application earlier. 

There's no need to be so rude at the people who offer their free time to help you.

[Norbert_B]

Stacking event structures occurs if you insert code already containing an event structure into another event structure. It may not be a problem right now, esp. if you use the event structure to capture different event (so, none of the structure capture an event from a source which is a source of an event for the other structure). But you have to keep in mind that stacking event structures implies a certain chain of execution of the events in order to continue the processing. That order might be the wanted one, but experience shows that most often, after some time, the user asks: "why do i always have to press this button after that one in order to proceed? why can't i press them in any order??"

hope this helps,
Norbert