LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

File Dialog and Default

Folks, I am trying to implement a behavior such everytime I open up my LabVIEW application, a windows box showing my saved/old files should automatically pop, before I use the "Esc" key to close the Windows Box.

 

I would appreciate any useful logic or suggestion on how I can implement the behavior.

 

Thanks in advance.

0 Kudos
Message 1 of 5
(2,721 Views)

You need to store the last saved file name in another file (I call it persistance file)... or you want to read a specific location for last saved file(s). And then you attached code (saved in verison 8.0) for displaying the message with custom behaviour.


I am not allergic to Kudos, in fact I love Kudos.

 Make your LabVIEW experience more CONVENIENT.


0 Kudos
Message 2 of 5
(2,708 Views)

Hi Moderator1983:

 

Thanks a lot for responding to my question, and especially for taking the time to create a simple code.  I downloaded and ran your code.  However, it is not the specific behavior I want.  The code you attached runs and displays the name of file(s) on the front panel, and when I presses the ESC key, it closes my front panel.  

 

The behavior I really want to accomplish is when I just Open up my application (not when I click on the RUN button) the Windows Dialog Box (File Dialog) should pop up with already saved/old files shown, this is just like saying taking a cursory look of saved files before beginning to run a new application.  Also, when the Windows Dialog Box pops, I should be able to press the ESc key to close the Windows Dialog Box, before clicking on the Run button to start running my application.

 

Once again, thanks for your earlier response, and much appreciated.

0 Kudos
Message 3 of 5
(2,687 Views)

An application should never be interacted with by the user unless the VI is running.  It sounds like you want the VI to do things before it is running which is the exact oposite way things should work.

 

You run your EXE and it runs your VI and the user interacts with it.  Your VI should work the same way.  Open the VI and do not change anything until the VI is running because that is how it will work if you make it an EXE.

0 Kudos
Message 4 of 5
(2,657 Views)

Hi Hoovahh:

 

Thanks for your contribution, and your assertion is very correct.  However, I have accomplished the behavior I wanted.

Regards

0 Kudos
Message 5 of 5
(2,646 Views)