LabVIEW
Multibutton App
Feel free to use "save for previous" before attaching your VI. Most here cannot open LabVIEW 2021 yet.
You already got some excellent advice why your code concept (that we have not seen!) is a bad idea overall.
Your CPU runs at GHz speed and even a fast gamer cannot press a front panel button more than a few times per second. From the perspective of the computer, literally eons pass between clicks. trivial to keep up!
It is also incorrect to use mouse-down events. Use a value changed and latch mechanical action buttons. (Mouse down events can be dangerous, because they also trigger on disabled controls and even indicators. They have their use, but that's not it!)
Not sure how (and why!) you are passing data to "other events".
All you need is one toplevel while loop and one event structure, assuming that the code inside each event can execute sufficiently fast. If each event triggers lengthy algorithms, use a producer-consumer architecture and do the processing elsewhere.
OK, I had a chance to look at your code and it is beyond repair. Obviously, you have not concept of dataflow and what an event structure actually does! The entire lower loop is completely constipated. it can only go to the next iterations once all event structures have fired, and unless they all fire exactly once per iteration, you'll get event queue buildup that can never be serviced.
At this point, you need to start with the learning resources listed at the top of the forum and familiarize yourself with the magic of dataflow and graphical programming. Then write your program without the use of any event structures! (event structures are an advanced topic with several landmines unless you really know what you are doing. They should only be used once you are very familiar with LabVIEW.
Also: There is no need to use value property nodes, but your code is peppered with them. (you must be coming form a text based programming background.). Don't use decorations to structure your code. They have no function.
You're not quite "thinking dataflow" yet. Remember, any node (VI, structure, whatever) cannot execute until ALL of its inputs have triggered. And a loop will not finish until ALL of its internal code has fired.
Since you have multiple event structures in your lower loop, that lower loop will never fire until ALL structures have fired, which isn't what you want.
You need only one single event structure, but one that can handle multiple events. Right click on the top of the Event Structure and click "Add Event". Then, that event structure will return when, and only when, exactly one event fires. You'll probably have one event per button.
Use shift registers to loop all of your data back around, and do one "thing" per iteration of the loop. Inside each event case you put the logic for that event. That way, the loop runs when anything happens, not when everything happens.
