You are here: NI Home > Support > Product Reference > Manuals > LabVIEW 8.5 Touch Panel Module Help

In the Project Explorer window, right-click the Touch Panel target, select Build Specifications, and select New»Application (EXE) from the shortcut menu to display this dialog box.

Use this dialog box to configure the build settings for building a Touch Panel VI into a Touch Panel application. This dialog box contains the following pages:

• Application Information—Defines the build options for the Touch Panel application. This page contains the following components:
  • Build specification name—Indicates the name of the Touch Panel build specification in the Project Explorer window.
  • Target filename—Indicates the name of the Touch Panel application on the Touch Panel target.
  • Same as top-level VI—Determines whether to use the top-level Touch Panel VI name as the Touch Panel application name.
  • Destination directory—Determines the destination directory of the Touch Panel application on the host PC.
  • Remote path for target application—Determines the destination directory of the PDA or Touch Panel application on the PDA or Touch Panel target.
  • Generate serial only—Treats the Touch Panel VI as if it were assigned a subroutine priority and executes parallel loops serially, which results in a smaller, faster Touch Panel application. By default, LabVIEW executes subroutine priority VIs without giving any time to the user interface thread for execution. You must include a wait in serial-only Touch Panel VIs to avoid the user interface from becoming unresponsive.
  • Enable debugging—Indicates whether to enable debugging in the Touch Panel application. Generating debugging information can significantly increase the size of the Touch Panel application. If the application is too large to debug, separate the large Touch Panel VIs into smaller subVIs.
  • Expression folding—Generates better performing and more efficient code by collapsing groups of nodes into single expressions that are easily recognized by C compilers. You cannot debug an embedded, PDA, or Touch Panel VI while using expression folding because expression folding eliminates some of the wires in the generated C code. If you overrun the bounds of an array or divide by zero, the application might crash.
  • Front panel scale factor—Determines how LabVIEW resizes front panel objects when you build the Touch Panel VI into a Touch Panel application. LabVIEW uses the scale factor to scale the coordinates and sizes of front panel objects so they appear correctly on the Touch Panel target. When you build a Touch Panel application using the default front panel scale factor and template size, LabVIEW reduces the user interface by a scale factor of two, so fonts appear as 14-point type, and the user interface is 240 x 300 pixels or 320 x 214, depending on the orientation.
  • Screen depth—Determines what type of bitmap the Touch Panel Module generates for images on the front panel when you build a Touch Panel VI into a Touch Panel application. For example, a screen depth of 16 generates 16-bit bitmaps. The default is 8.
• Device Information—Shows the Touch Panel target for which this build specification applies. This page contains the following components:
  • Target device—Indicates the target for this build specification.
  • Processor—Indicates the different processors for which you can build the Touch Panel VI into a Touch Panel application.
• Source Files—Determines the files to include in the Touch Panel application you are building. This page contains the following components:
  • Files—Lists the VIs you can include in the Touch Panel application you are building.
  • Top-level VI—Indicates which VI is the top-level VI.
  • Additional files—Shows the additional files to add to the Blackfin application. You can add .c, .dlb, or .ldf files.
  • Always Included (*.vi)—Specifies the dynamic VIs always to include in the application, even if the top-level VI does not contain references to the files.
• Source File Settings—Displays which VIs have VI-level C code generation options. You must select a VI to see the code generation options.
  • Generate serial only—Treats the Touch Panel VI as if it were assigned a subroutine priority and executes parallel loops serially, which results in a smaller, faster Touch Panel application. By default, LabVIEW executes subroutine priority VIs without giving any time to the user interface thread for execution. You must include a wait in serial-only Touch Panel VIs to avoid the user interface from becoming unresponsive.
  • Enable debugging—Indicates whether to enable debugging in the Touch Panel application. Generating debugging information can significantly increase the size of the Touch Panel application. If the application is too large to debug, separate the large Touch Panel VIs into smaller subVIs.
  • Expression folding—Generates better performing and more efficient code by collapsing groups of nodes into single expressions that are easily recognized by C compilers. You cannot debug an embedded, PDA, or Touch Panel VI while using expression folding because expression folding eliminates some of the wires in the generated C code. If you overrun the bounds of an array or divide by zero, the application might crash.
• Machine Aliases—Lists the targets in the project that support hosting shared variables. PDA and Touch Panel targets do not support hosting shared variables. Use the Machine Aliases category to overwrite the default IP address of the shared variable host target so you can move the shared variable to a different host without rebuilding the application. This page contains the following components:
  • Aliases list—Shows the physical addresses of the targets in the project that can host shared variables.
  • Deploy aliases file—Indicates you want to create the aliases file when you build the PDA or Touch Panel VI into a PDA or Touch Panel application, and deploy the aliases file when you deploy the application to the PDA or Touch Panel target.
    
    The PDA Module and Touch Panel Module disable the Deploy aliases file checkbox if you are using a target that eMbedded Visual Tools enables. If you are using a target that eMbedded Visual Tools enables, you must manually create and deploy the aliases file.
• Generated Files—Displays a preview of the directory structure and filenames in the build. Use this preview to determine if you need to change file destinations or other settings.

My Profile | Privacy | Legal | Contact NI   © 2009 National Instruments Corporation. All rights reserved.   |