This Document is not yet Rated

Rate this Document

How do I Force the LabVIEW Operator Interface to Not Load Any Sequence Files When Executed?

Primary Software: TestStand
Primary Software Version: 3.5
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem:
When I execute my LabVIEW Operator Interface there are sequence files loaded already. Why are they loading and how do I stop these sequence files from loading?

Solution:

The sequence files that you see are the files that were loaded the previous time the Operator Interface was closed.

• In TestStand 3.5 these files are stored in an .ini file named OperatorInterface.ini that is located in the C:\Documents and Settings\<username>\Local Settings\Application Data\National Instruments\TestStand 3.5\ directory.
  
• In TestStand 4.0 these files are stored in an .xml file named UserInterface.xml that is located in the C:\Documents and Settings\<username>Local Settings\Application Data\National Instruments\TestStand 4.0\ directory.

When you execute the Operator Interface there is a subVI called Configure Application Manager.vi that gets called.  Inside of this subVI there is a property node that uses the Application Manager reference to call ReloadSequenceFilesOnStart:

To stop these sequence files from loading, change the enum constant to the option ReloadFile_None. The next time that the Operator Interface is executed, the previous sequence files will not be loaded.

Related Links:
Developer Zone Tutorial: Adding Custom Commands to the LabVIEW Operator Interface


Attachments:


- ReloadSequenceFilesOnStart.GIF



Report Date: 10/25/2006
Last Updated: 11/14/2007
Document ID: 42OAQUDR

Your Feedback!	Poor  |  Excellent							Yes	No
Document Quality?							Answered Your Question?
	1	2	3	4	5
Document needs work? Please tell us why.
Please Contact NI for all product and support inquiries.