Is it ok to trigger 2 event loops off the same control?

[sfrosty]

I have two event loops which need to trigger when the Exit button is clicked on. Is it ok to trigger both loops off the same control? It has been working great, but I'm not sure if there could be an issue. Please see below. Thank You!

[crossrulz]

I would just question why you have two event structures in the same VI.  In general, you should just have one place that handles GUI events and then you can pass commands off to other processes using queues.

[sfrosty]

Ahhh! Good point. I think it's because I decided to include a separate while loop to control my menu after the main code was built and didn't think of inlcluding the menu event in the original event structure. Another point may be that I have  50 ms wired to the timer in the MENU event structure and don't want any delay in the MAIN Event structure. Not sure if this is a valid point.

[crossrulz · Accepted solution]

---

@sfrosty wrote:

Another point may be that I have  50 ms wired to the timer in the MENU event structure and don't want any delay in the MAIN Event structure. Not sure if this is a valid point.

---

Why?  Are you doing something else in that loop?

I would recommend moving your menue stuff into your main event loop.  You will thank yourself later.

[sfrosty]

Will do! Thanks for your help!

[sfrosty]

Oops! I misread your question:

Why?  Are you doing something else in that loop?

Yes, I'm using the MENU timer event case (50ms) to process an Exit global!

[sfrosty]

Waiting on Exit global timer event.

[sfrosty]

Oh, and I won't need the Exit global loop if I place the menu event case in the main event case.

[Dennis_Knutson]

That makes no sense. You should just have a value change event for the exit button. No need for a global and certainly no need to read one in the timeout event.

[sfrosty]

Got it!