How to make a file explorer work under certain conditions

Question

Good afternoon,
I have built a VI that is basically a file explorer that lets you import data to another application, when a button is clicked, you can navigate throught the directories of your pc searching for a txt file to import and plot some ghraphs. I used the property node "Visible" to show up this file explorer as a window, so every time i click the button, it shows up, but I realize it is processing even if its not being used, like a process running in second plan, thats why I want to make it different, I want to make it run only when the button aforementioned is on true, and to make it I have tried stuff like wiring the button to the loop condition, using a case structure with the button wired and nothing seems to work. How could I do that?
I appreciate your help,
Lucas Faquim
Attachments:
Temperatura.vi ‏337 KB

Answer 1

Faquim wrote:
First of all, thank you for your answer, Hooovahh. I am not an expert programmer, I really dont know the problems around the infinite loop, and dont know what are the issues around thhe abort execution, could you tell me?
To understand this idea, think of yourself as a VI.  You're sent to cook a full meal in the kitchen.  This meal is complex enough it'll require several burners, the sink, a cutting board, and trips to the fridge and cupboards.  I tell you to start cooking and you go about your business getting things going.  At some point, I come in and drag you out of the kitchen and don't allow you to go back.  What state is the kitchen in?  Is the fridge open?  Is the freezer open?  Are the burners on?  Is the oven on?  Is the oven closed?  Will things on the stove boil over creating a mess and potentially a fire?  Who knows?  You're creating the same mess when you hit the abort button.  You're forcing yourself into an uncertain situation that may cause more problems than taking the thirty seconds it'd take to turn your burners off, turn off the oven, and close the fridge door.  You WANT to have a cleanup routine in case things need to stop similar to getting the kitcen into a safe state before leaving.
With an embedded system, there isn't the typical user interface so if it stops, it's likely stopped for a LONG time.  These typically run infinitely until something goes wrong and they shut themselves down.  When you can put a stop button on the front panel and use that, it makes worlds more sense than leaving the kitchen in disarray.