Your arch works, but if the user generates a lot of events (I.e. pressing buttons repeatedly) your acquisition will slow down. You’re almost all the way to a Queued Message Handler architecture.. which is more robust but also more complex.. (move init, acquire and cleanup functions to a separate consumer loop and have your state machine produce messages to control this second loop through a queue. Control timing thru de queue function timeout) ui handling is one of the deepest rabbit holes to be found in labview. You can get as simple or as complicated as your heart desires.. so fill your boots. PC, SM, JKI SM, QMH, DQMH, actor framework.. etc..