Third MHL not triggering

[CatDoe]

I have been trying to debug the reason why my third MHL (should work in parallel with the main MHL) will not work. For instance, the messages sent upon clicking the X button work well. The message sent in timeout to the main MHL works fine, but then the main MHL loop to the third parallel MHL loop does not even appear to get into the queue. 

Any help is appreciated. I have tried numerous attempts over several days to rectify this situation.

Code is attached in the ZIP file. I would like to keep the event handling loop independent from the parallel data saving loop if possible.

Goal is:

1. Timeout - create a single call to trigger Add Start Line

    - triggered by the event handling loop on timeout

    - message sent to MHL 

    - MHL sends message to parallel data saving loop

2. Cancel button (X button on front panel) value change

   - Save last settings - MHL queues message to save data in parallel loop

   - Confirm Quit - should trigger both MHL and parallel loop to exit

Right now, some of the parallel messages are created by the event handling loop because I cannot get the independent structure to work.

[Bob_Schor]

Hello, CatDoe.  I'm having trouble making sense out of the files you sent in your ZIP folder.  Where is the LabVIEW Project File (.lvproj) that shows all of the VIs in their "virtual folders" (much easier to view that way, as you can see the entire "tree" and all of the VIs, at least in name, at the same time).  I also can't figure out which is supposed to be the Top Level VI that can help me make sense of what you are trying (with apparently some difficulty) to do.

I recommend that you take your existing LabVIEW Project (which I assume is located within a single Windows folder, possibly with many sub-folders) and zip that up by sending it to a "compressed file".  You can substitute a "simplified Top level VI" and simplified MHL and Event Loops, but let us open one thing (the LabVIEW Project file) and have everything at hand, including the Top Level VI.

Bob Schor

P.S. -- when attaching LabVIEW code, it is helpful to indicate the LabVIEW version of the code.  Probably 95% of the Forum users will be able to open LabVIEW 2018 code, 50% to open LabVIEW 2021 code, and 10% LabVIEW 2022 code (and most of those might be First Time Users, but that's just a guess ...).