As they say, "Close, but no cigar". You almost have the right idea of Producer/Consumer with Event structure. Here's a suggestion:
Create a different Enum, call it "State". Have it take on the following values: "Show Video", "Stop Video", "Open Video", "Open Button", and "Quit". Create a Queue (not a Notifier) for this Enum. [Why a Queue instead of a Notifier? A Notifier only "remembers" the last item, so if you push two buttons at the same time, you might not "see" both of them]. [Another thing to think about -- what if you push Start Video twice in a row, without pushing Stop Video in between? What do you want to have happen?].
Make your Event loop very tiny -- the only thing it should do is to Enqueue the appropriate Enum value -- it should not do any other processing! [Possible exception -- you could have the Stop button Value Change case not only put "Quit" on the Queue, which should be set to stop the Consumer loop, but, as a "side effect", it can stop the Producer loop, too. This means you don't need "Stop2"].
Now put all the "Action code" currently in your Event Loop in the Consumer Loop (you currently have Show Video and Stop Video code there -- put the Open Video and Open Image code there, as well).
Notice that you've relegated to the Event loop only "Events", things that happen randomly and unpredictably (like users pushing buttons), so very little time is spent here.
If you want to make this even more "transparent" to experienced LabVIEW programmers, put the Event loop on top (and, as noted above, make it tiny).
Bob Schor
