LabVIEW 2013 Touch Panel Module Help
»View Product Info
Requires: DSC Module or Touch Panel Module
Use this page of the Application Properties dialog box to configure advanced settings for a Touch Panel application.
This page includes the following components:
- Enable debugging—Enables debugging for the application.
- Wait for debugger on launch—Sets the application to load but not run until the user enables it to run through the LabVIEW debugging controls. Place a checkmark in the Enable debugging checkbox to activate this option.
- Copy error code files—Adds copies of XML-based LabVIEW error code text files from the labview\project\errors and labview\user.lib\errors folders to the run-time engine.
|Note You must manually create an errors folder in the labview\user.lib directory to organize your error code files.|
- Use the default project aliases file—Copies the project aliases file with the application to the local destination directory. If you remove the checkmark from this checkbox, the Select Project File dialog box appears and you can select another aliases file in the project.
- Aliases file in project—Specifies the aliases file to use with the application or shared library if Use the default project aliases file does not contain a checkmark. Click the Browse Project button to display the Select Project File dialog box, which you can use to select an aliases file.
- Use the default LabVIEW Configuration file (LabVIEW .ini)—Associates the LabVIEW configuration file with the application. If you remove the checkmark from this checkbox, the Select Project File dialog box appears, and you can select another configuration file in the project.
- Configuration file in project—Specifies the configuration file to use with the application if you do not enable Use the default LabVIEW Configuration file (LabVIEW .ini). Click the Browse Project button to display the Select Project File dialog box, which you can use to select a .ini file in the project.
- Pass all command line arguments to application—Passes all arguments as user-defined arguments to the application when you launch it from the command line. Only the arguments after two hyphens (--) in the command line pass to the application as user-defined arguments, unless you place a checkmark in the checkbox. Use the Application:Command Line Arguments property to read the user-defined command-line arguments passed when the application launches.
- Enable ActiveX server—Enables the ActiveX server so the application can respond to requests from ActiveX clients. The functionality of the ActiveX server in the application is a subset of the LabVIEW ActiveX server. When you build an application myapp.exe, LabVIEW also creates an ActiveX type library myapp.tlb. The type library defines an application class and a virtual instrument class and exports both Application properties and methods and VI properties and methods. When you distribute the application, include the type library with the executable file.
The name of the application that you enter in the ActiveX server name text box uniquely identifies the application in the system registry. After you build the application, run it at least once to enable registry with the system. After the application is registered, ActiveX clients access the server objects using progIDs. For example, if the ActiveX server name is myapp, clients instantiate an application object using the progID myapp.application.
If you are packaging the application into an installer build specification, place a checkmark in the Register COM checkbox for the application file on the Source File Settings page of the Installer Properties dialog box so the installer registers the ActiveX server.
|Note If you enable the ActiveX server, you must save the application build specification after you build the application for the first time.|
- ActiveX server name—Specifies the prefix of the progID for the application. This text box is enabled when you place a checkmark in the Enable ActiveX server checkbox.
- Enable Enhanced DSC Run-Time support—This option only appears if you have the LabVIEW Datalogging and Supervisory Control (DSC) Module installed. Builds the application with the enhanced DSC Module Run-Time Engine. The DSC Module Run-Time Engine adds additional support for programmatic project library and shared variable management in applications that you build with the DSC Module. You must place a checkmark in this checkbox in the following situations:
- The application you want to build uses VI Server references to modify a library file programmatically.
- The application you want to build uses the Save to Library VI.
If you do not enable the enhanced DSC Module Run-Time Engine in these two situations, LabVIEW returns error code 1055 when you run the built application, shared library, or .NET interop assembly.
|Note Enabling this option increases the file size and reduces the start-up performance of the built application, shared library, or .NET interop assembly.|
- Generate build log file—Specifies whether to create a log file for the build. The build log file lists all files contained in the build, including subVIs you do not specify as Startup VIs or Always Included on the Source Files page. The log file also contains general build information such as build start and end time, the build specification and project name, and any errors that occurred during the build.
- Log file path—Specifies the path to save the build log file.
- Use LabVIEW 8.x file layout—Specifies to use a flat file layout to store source files inside a stand-alone application, shared library, or Web service. LabVIEW enables this option by default for build specifications you load from LabVIEW 8.6 or earlier. National Instruments recommends you disable this option for applications you develop in LabVIEW 2009 or later.
- Enable SSE2 optimizations—Configures this build specification to include SSE2 instructions when compiling the included VIs. Remove the checkmark from this checkbox if the target for this build specification does not support SSE2 instructions.