Company Events Academic NI Developer Zone Support Solutions Products & Services Contact NI MyNI

LabVIEW 8.2 Features and Changes

LabVIEW 8.2 Help
August 2006

NI Part Number:
371361B-01

»View Product Info

Refer to the LabVIEW 8.2 Upgrade Notes for a complete list of new features and changes, for information about upgrade and compatibility issues specific to different versions of LabVIEW, and for upgrading instructions.

Refer to the readme.html in the labview directory for known issues, additional compatibility issues, and information about late addition features in LabVIEW 8.2.

LabVIEW Documentation

LabVIEW 8.2 includes the following documentation enhancements:

  • A Submit feedback on this topic link appears at the bottom of all LabVIEW Help topics. To provide feedback on a help topic, click and complete the Documentation Suggestion Details form. This link only appears in English versions of the LabVIEW Help.
  • Concept topics include a navigation table in the upper, right-hand corner of the help topic. Click a link in the table to jump to the related subtopic.

New Example VIs

Refer to the New Examples for LabVIEW 8.x folder on the Browse tab of the NI Example Finder to view descriptions for and launch example VIs added to LabVIEW 8.x.

Launch Time Improvement

LabVIEW 8.2 launches faster than LabVIEW 8.0 due to performance optimizations.

Block Diagram Enhancements

LabVIEW 8.2 includes the following enhancements to the block diagram and related functionality.

Default Color Changes

The default colors of the following block diagram components changed to improve visibility:

  • Error cluster wires and terminals appear dark yellow instead of pink on the block diagram.
  • Coercion dots appear red instead of gray by default. To change the color of coercion dots, select Tools»Options and select Colors from the Category list. Remove the checkmark from the Use default colors checkbox and click the Coercion Dots color box to select a different color.

Removing Breakpoints from a VI Hierarchy

From a VI, select Edit»Remove Breakpoints from Hierarchy option to remove all breakpoints from the VI hierarchy. You must manually remove breakpoints in dynamically called VIs or VIs referenced by the Static VI Reference function.

Performance Optimized with Constants

LabVIEW uses constant folding to optimize the performance of VIs. With constant folding, LabVIEW stores constant values when it compiles VIs instead of calculating them at run time. For constants wired to structures, LabVIEW calculates the output values of the structures when it compiles VIs and stores the values so they are available at run time.

You can display constant folding hash marks on the block diagram by selecting Tools»Options, selecting Block Diagram from the Category list, and placing checkmarks in the Show constant folding of wires and Show constant folding of structures checkboxes. When you place a checkmark in the Show constant folding of wires checkbox, gray hash marks appear on the wires attached to constants that are constant folded. When you place a checkmark in the Show constant folding of structures checkbox, gray hash marks appear inside structures that are wired to constants. The hash marks might not appear in a VI until after you run or save the VI.

LabVIEW 8.2 also folds computed constants you wire to Case structure selector terminals and While Loop conditional terminals.

Miscellaneous Block Diagram Enhancements

LabVIEW 8.2 includes the following miscellaneous enhancements to the block diagram.

  • When you right-click the reference out output of a Property or Invoke Node and select Create from the shortcut menu, the Create menu displays the properties or methods in the same class as the Property or Invoke Node.
  • The Visible Items:Hierarchy Lines Visible property accepts the following values: If Visible, LabVIEW always displays lines to outline the hierarchy of the items as vertical and horizontal lines to the left of the items in the tree control. If Invisible, the hierarchy lines are always invisible. If OS Default, LabVIEW displays the hierarchy lines if trees in the operating system show hierarchy lines.

Front Panel Enhancements

LabVIEW 8.2 includes the following enhancements to the front panel and related functionality.

Setting Background Images for Panes

You can set and import background images for panes. Right-click the scroll bar of a pane and select Properties from the shortcut menu. In the Pane Properties dialog box, select an image from the Background list.

To select an image that does not appear in the Background list, click the Browse button. LabVIEW supports BMP, JPEG, and PNG graphic formats for background images. You also can use the Background Image property to set a pane background image programmatically.

Note  If you select an image that does not appear in the Background list, LabVIEW does not add that image to the Background list permanently. To add an image to the list permanently, you must save the image in the labview\resource\backgrounds directory.

When you save a VI that contains a pane with a background image, LabVIEW saves the pane background image with the VI.

Locking Knobs and Dials at Minimum and Maximum

By default, knobs and dials cannot rotate past their minimum or maximum values.

To disable this locking behavior, right-click the knob or dial, select Properties from the shortcut menu, and remove the checkmark from the Lock at minimum and maximum checkbox. Locking prevents a knob or dial from jumping from minimum to maximum or maximum to minimum values. Disabling this behavior might cause unintended jumps between values.

In LabVIEW 8.2, when you open a VI last saved in LabVIEW 8.0 or earlier, locking is disabled. To enable locking, place a checkmark in the Lock at minimum and maximum checkbox.

Multiple-Item Dragging within Tree Controls and Listboxes

You can drag and drop multiple items from and to tree controls and listboxes. Right-click the tree control or listbox and select Selection Mode»0 or More Items or Selection Mode»1 or More Items from the shortcut menu to enable multiple-item dragging and dropping. Initiating a drag with multiple items selected moves all the selected items.

Digital Waveform Graph Enhancements

Refer to the Fundamentals»Graphs and Charts book on the Contents tab in the LabVIEW Help for more information about digital waveform graphs.

LabVIEW 8.2 includes the following enhancements to digital waveform graphs.

Setting Line Thickness

Line Style replaces Thick Line Location in the shortcut menu of the digital waveform graph plot legend. Right-click the plot in the plot legend and select Line Style from the shortcut menu to set the line thickness. LabVIEW 8.2 includes a new Line Style option to thicken the entire line.

Darkening Compare Data

If a digital waveform graph includes digital data in both drive and compare logic states, by default the compare data appears darker on the plot than the drive data. If you do not want to darken compare data, right-click the plot and select Advanced»Darken Compare Data from the shortcut menu to remove the checkmark. You also can use the Darken Compare Data property to darken compare data programmatically.

Note  This feature primarily applies to users generating digital I/O signals. Refer to the Fundamentals»Graphs and Charts»Concepts»Customizing Graphs and Charts book on the Contents tab of the LabVIEW Help for more information about compare data.

Miscellaneous Front Panel Enhancements

LabVIEW 8.2 includes the following miscellaneous enhancements to the front panel.

  • In LabVIEW 8.0, the first time you display a caption for a front panel object, LabVIEW moves the label to the side. In LabVIEW 8.2, LabVIEW hides the label and displays only the caption.
  • In the XY Graph Properties dialog box, the Show optional plane pull-down menu and the options to configure the plane you select moved from the Scales page to the Appearance page.
  • You can use the Coloring tool to change the background color of a system table.
  • You can change the color of the headers and cells of a system multicolumn listbox, listbox, table, or tree control.
  • The Reinitialize to Default Value, Cut Data, and Paste Data options are not available in the shortcut menu of an indicator when the VI is in run mode. These shortcut menu options are available only for controls in run mode.
  • To size a tab control to fit its contents, right-click the tab control and select Advanced»Size To Fit from the shortcut menu.
  • When you right-click an enumerated type control, ring control, or combo box control and select Edit Items from the shortcut menu, you must double-click in a cell to edit an item in the Items or Values column. This change also applies when you right-click the text labels for a slide control or knob and select Edit Items from the shortcut menu.
  • In LabVIEW 8.0, when you select File»Apply Changes from the Control Editor window, LabVIEW preserves the label, caption, and value of the original control. In LabVIEW 8.2, LabVIEW applies all the changes you make in the Control Editor window and does not preserve any information from the original control. This behavior applies only to custom controls and not to type definitions.
  • LabVIEW does not include hidden plots when you autoscale the axes of a graph or chart. If you want to include the hidden plots when you autoscale, make the hidden plots transparent instead. Right-click the plot legend and select Color from the shortcut menu to change the color of the plots.
  • Windows Radio buttons and checkboxes in LabVIEW are consistent with the behavior of radio buttons and checkboxes in Windows. You can toggle radio buttons and checkboxes only using the spacebar. You can toggle dialog box buttons with the <Enter> key on the alphanumeric keyboard, the <Enter> key on the numeric keypad, or the spacebar. The LabVIEW keyboard shortcuts <T> and <F> do not toggle dialog box buttons.
  • LabVIEW 8.2 includes new tokens for advanced editing of the time stamp control. Right-click the control and select Properties from the shortcut menu to display the Time Stamp Properties dialog box. On the Format and Precision page, select the Advanced editing mode option to display the Absolute time format codes list. LabVIEW 8.2 includes following new format codes.

    Format Code Value
    <%^<>T> Universal time container
    <%z> Difference between locale time and universal time

Environment Enhancements

LabVIEW 8.2 introduces the following enhancements to the LabVIEW environment.

Automatic Saving for Recovery

In the event of an irregular shutdown or system failure, LabVIEW backs up any modified VI (.vi), VI template (.vit), control (.ctl), or control template (.ctt) files open at the time of the shutdown or failure to a temporary location. LabVIEW does not back up projects (.lvproj), project libraries (.lvlib), XControls (.xctl), or LabVIEW classes (.lvclass).

If LabVIEW automatically saves files before an irregular shutdown or system failure, the Select Files to Recover window appears the next time you launch LabVIEW. Select the files you want to recover and click the Recover button. If you do not want to recover any files, deselect all files and click the Discard button. Click the Cancel button to move all selected files to the LVAutoSave\archives subdirectory of the default data directory.

Select Tools»Options and select Environment from the Category list to enable or disable saving for recovery and to specify how often LabVIEW should back up files.

Dialog Box Enhancements

LabVIEW 8.2 includes the following dialog box enhancements.

Options Dialog Box Enhancements and Changes

LabVIEW 8.2 includes the following Options dialog box enhancements. Refer to the National Instruments Web site for information about workarounds for these deprecated options.

  • The Performance and Disk page no longer exists, including the Check available disk space during launch and Run with multiple threads options.
  • On the Front Panel page, the Override system default function key settings and the Use smooth updates during drawing options no longer exists.
  • On the Block Diagram page, the Show wiring guides option no longer exists.
  • On the Paths page, the Library Directory option in the pull-down menu no longer exists.
  • On the Environment Options page, the Use abridged menus option no longer exists.
  • On the Environment page, the Enable Just-In-Time Advice checkbox no longer contains a checkmark by default.
  • On the Block Diagram Options page, the Show subVI names when dropped checkbox also applies to global variables. Make sure this checkbox contains a checkmark if you want to display the label of the global variable when you place it on the block diagram.
  • On the Web Server: Visible VIs page, the Currently selected VI option changed to the Visible VI option.

LLB Manager Enhancements

LabVIEW 8.2 includes the following enhancements to the LLB Manager window.

  • A Browse button appears to the right of the Directory field. Click this button to navigate to the LLB you want to modify.
  • A Delete button appears in the toolbar. Select a file in the Files list and click this button to remove the selected file from the LLB.
  • You can sort by column in the Files list by right-clicking the columns.

Data Binding Page

LabVIEW 8.2 includes the following enhancements to the Data Binding page of the Properties dialog box of all front panel controls:

  • The Current Network Item Selected and Current Project Item Selected text boxes changed to the Path text box.
  • The Mode section changed to the Access Type pull-down menu.
  • The Blink while Alarm On checkbox no longer appears.
  • The Browse button that appears when you select Shared Variable Engine (NI-PSP) from the Data Binding Selection pull-down menu launches the Select Source Item dialog box instead of the Select Network Item dialog box. The Select Network Item dialog box no longer exists.
  • The Network-Published Source pull-down menu appears in the Select Source Item dialog box instead of on the Data Binding page.

Miscellaneous Dialog Box Enhancements

LabVIEW 8.2 includes the following miscellaneous dialog box changes:

  • The VI Metrics window includes a row in the Metrics Statistics table to display the average of all the values in a column. You also can exclude files located in a specific folder by placing a checkmark in the Exclude files in this folder from statistics checkbox.
  • In the VI Properties dialog box, the Security page changed to the Protection page.
  • The Polymorphic VI window includes a Show License Warning button that appears if the polymorphic VI belongs to a licensed project library where the license is either in evaluation mode or invalid. Click this button to display a warning message. Click the Help button in the warning message for more information about the license status.
  • In the Edit Format String dialog box and Edit Scan String dialog box, you can select SI notation from the Selected operation pull-down menu as the conversion type.
  • In the Export Simplified Image dialog box, the Save to clipboard option changed to Export to clipboard.
  • In the Create Instrument Driver VI dialog box, None is no longer an option in the Output data type pull-down menu on the Control setup page.
  • In the Error Code File Editor window, the Current Error Code and Description option changed to the Error code and Error text options.

Displaying Hidden Controls and Indicators

You can display all hidden controls and indicators on the front panel of custom controls and global variables by selecting Edit»Show Hidden Controls and Indicators. This option is available only in the Edit menu of a custom control or global variable.

You also can display controls and indicators for VIs that are not custom controls or global variables by running the ShowHidden Core VI in the labview\project\_ShowHidden directory.

Error List Window Enhancements

In the Items with errors list in the Error list window, broken items appear with a red X glyph beside the item name. LabVIEW sorts these items to the top of the Items with errors list. Items that cause errors in other items because you are editing them appear with a pencil icon beside the item name. Items that appear with no icons beside the item name have errors because an item on which they depend is has errors.

Find and Replace Enhancements

LabVIEW 8.2 includes the following enhancements to the find and replace operations and related functionality.

  • In the Text Search Options, the Ignore clones checkbox ignores any front panel clones, or reentrant front panels, when you search for text in a VI.
  • In the Find dialog box, the Select Object button appears with the title of the object you select instead of the filename of the object.
  • The Search Results Window appears only if LabVIEW finds more than one object during a search. If LabVIEW finds only one object, LabVIEW highlights the object on the front panel window or block diagram window.
  • The Find dialog box also finds and replaces Express VIs and nodes such as the Match Regular Expression function and variables.

Managing Open Windows

The Window menu displays a maximum of 10 open windows. You can manage all open windows by selecting Window»All Windows or by pressing <Ctrl-Shift-W> to display the All Windows dialog box. You can show or close a window or save the item that corresponds to the window by clicking the corresponding button on the right side of the dialog box.

Palette Enhancements

LabVIEW 8.2 includes the following palette enhancements:

  • You can use the Organize Favorites dialog box to change the order of the items in the Favorites palette category.
  • The Menu Documentation dialog box changed to the Palette Documentation dialog box. The Menu Description field changed to Palette Description.
  • If a palette belongs to a project library, you can view the path to the project library. Select Tools»Advanced»Edit Palette Set, right-click a palette and select Display Path To Palette File from the shortcut menu. LabVIEW displays the actual path of the palette and the path to the owning library, if the palette belongs to a library.
  • The Edit Controls and Functions Palette Set dialog box includes the Preview changes before saving checkbox. Place a checkmark in the Preview changes before saving checkbox and click the Save Changes button to display the Preview Palette Changes dialog box.
  • The Drop VI shortcut menu item changed to Place VI. This shortcut item appears if you right-click a VI on the Functions palette.
  • LabVIEW 8.2 includes palettes that remain empty until you install an add-on. For example, the Control Design & Simulation subpalette on the Controls palette is empty until you install one of the LabVIEW Control Design & Simulation products.

Saving a Duplicate Hierarchy

You can save a VI and its subVIs as a duplicate hierarchy without having to create a source distribution. Select File»Save As and select the Duplicate hierarchy to new location option to save the VI and its hierarchy to a new location.

Miscellaneous Environment Enhancements

LabVIEW 8.2 includes the following miscellaneous enhancements to the front panel:

  • LabVIEW no longer displays a watermark on the subVIs in a subpanel of a VI in the Evaluation or student versions of LabVIEW. LabVIEW also no longer displays a watermark on the debug deployment version of LabVIEW.
  • If you do not have a valid license specific to the version of LabVIEW that you purchased, you might not be able to edit polymorphic VIs.
  • You can create a reference to a control in a strict type definition by right-clicking the control in the type definition and selecting Create»Reference from the shortcut menu.
  • The View menu includes the This VI's Library, This VI's XControl, or This VI's Class item which highlights the project library, XControl, or LabVIEW class to which the current VI belongs in the Project Explorer window. The menu item changes according to the type of library that owns the VI. If the library, XControl, or class is not in a LabVIEW project, LabVIEW opens a new window that contains only the library, XControl, or class to which the current VI belongs.
  • In LabVIEW 8.0, the Help»Explain Errors menu item is not available in the Getting Started window. In LabVIEW 8.2 this menu item is available in the Getting Started window.
  • Mac OS To display or hide the Context Help window, select Help»Show Context Help or press the <Command-Shift-H> keys. The <Command-H> keyboard shortcut hides the open LabVIEW application. Refer to the LabVIEW Help for more information about customizing keyboard shortcuts.
  • Select Tools»Instrumentation»Advanced Development to access options for advanced development in LabVIEW using instrument drivers, including:
    • Show Driver Guidelines displays the Instrument Driver Guidelines from the National Instruments Instrument Driver Network at ni.com/idnet in a Web browser.
    • Show Icon Art Glossary displays the Icon Art Glossary on from the National Instruments Instrument Driver Network at ni.com/idnet in a Web browser.
    • Other Resources displays Development Tools and Resources from the National Instruments Instrument Driver Network at ni.com/idnet in a Web browser.

New and Changed VI, Function, and Node Enhancements

LabVIEW 8.2 includes the following new and changed VIs and functions. Refer to the VI and Function Reference book on the Contents tab of the LabVIEW Help for more information about VIs, functions, and nodes.

New VIs and Functions

LabVIEW 8.2 includes the following new VIs and functions.

Advanced File VIs

The Advanced File Functions palette includes the following new VIs:

Digital Waveform Functions

The Digital Waveform palette includes the following new functions:

Mathematics VIs

The Mathematics palette includes the following new VIs in the LabVIEW Full and Professional Development Systems:

.NET VIs

The .NET palette includes the following new VIs:

Scaling VIs

The Scaling palette includes the following new VIs:

Signal Processing VIs

The Signal Processing palette includes the following new VIs in the LabVIEW Full and Professional Development Systems:

TDM Streaming VIs and Functions

The TDM Streaming palette includes the following new VI and functions:

The Storage palette includes the following new VIs:

  • Convert TDM to TDMS VI
  • Convert TDMS to TDM VI

Refer to the TDM Streaming File Format section of this document for information about the TDM streaming file format.

Changed VIs, Functions, and Nodes

The following VIs, functions, and nodes changed in LabVIEW 8.2.

DataSocket functions

The DataSocket palette includes the following changed VIs:

  • The DataSocket Read function has a status output, which reports warnings or errors from a PSP server or FieldPoint controller.

Mathematics VIs

In the LabVIEW Base Package, the A x B VI includes the new instances Vector x A and Complex Vector x A.

The Mathematics palette includes the following changed VIs in the LabVIEW Full and Professional Development Systems:

  • The Exponential Fit VI includes a new Weight input that specifies the array of weights for the observations (X, Y). The negative values that often result from signal noise no longer cause the exponential fit to fail.
  • The GCD of p(x) and q(x) VI includes a new algorithm input that specifies the algorithm the VI uses to compute the polynomial greatest common divisor.
  • The General Polynomial Fit VI includes a new Weight input that specifies the array of weights for the observations (X, Y).
  • The Histogram, Histogram PtByPt, General Histogram, and General Histogram PtByPt VIs include a Histogram Graph output that displays the bar graph of the histogram of the input sequence X. The y-axis is the histogram count, and the x-axis is the histogram center values of the intervals (bins) of the histogram.
  • The LCM of p(x) and q(x) VI includes a new algorithm input that specifies the algorithm the VI uses to compute the polynomial least common multiple.
  • The Partial Fraction Expansion VI includes a new option input that specifies how the VI handles the co-factors of Numerator and Denominator.
  • The Sylvester Equations VI includes a new matrix type input that specifies the types of inputs A and B, which speeds up the computation of X.
  • The Direction Cosines input of the Array instance of the 3D Cartesian Coordinate Rotation (Direction) VI changed to Rotation Matrix.

Numeric Functions

The Numeric palette includes the following changed functions:

  • The Quotient & Remainder function produces accurate answers when you use large negative 64-bit divisors.
  • The anything input of the Swap Bytes and Swap Words functions changed to data. You can wire string, tag, path, Boolean, non-integer numeric, enumerated type, error cluster, picture, matrix, and array and cluster data of such types and you can pass the data unchanged. For any 16-, 32-, and 64-bit integers wired to the input the function swaps every byte pair in each word or every word pair in each longword. You cannot wire occurrences, all refnum types, or variants to the input.
  • On x86-based platforms, the Scale By Power Of 2 function produces the correct answer when both the x and n inputs are floating-point numeric.

Protocols VIs and Functions

The Protocols palette includes the following changed VIs and functions:

  • The UDP Open function and UDP Multicast Open VI have a new port output that returns the port number the function used.
  • The UDP Open function and UDP Multicast Open VI have a new net address input, on which network address to listen.
  • The address input of the TCP Open Connection function changed from optional to recommended.
  • The TCP Listen VI includes a resolve remote address input that indicates whether to call the IP to String function on the remote address. The default is TRUE.

Quadratic Programming VI

The Quadratic Programming VI includes the following changes:

  • The Quadratic Programming VI is a polymorphic VI with the following instances: Quadratic Programming IP and Quadratic Programming AS. The Quadratic Programming IP instance has the same functionality as the Quadratic Programming VI in LabVIEW 8.0. The Quadratic Programming AS instance finds the minimum using an active set algorithm.
  • Both instances of the Quadratic Programming VI include a start input that specifies the point in n dimension at which the optimization process starts.
  • Both instances of the Quadratic Programming VI include a max time (sec) input that specifies the maximum amount of time LabVIEW allows between the start and the end of the optimization process.
  • The Quadratic Programming AS instance of the Quadratic Programming VI includes a warm start? input that indicates whether to allow a warm start of the optimization.

Signal Processing VIs

The Signal Processing palette includes the following changed VIs in the LabVIEW Full and Professional Development Systems:

  • The Median Filter VI includes new left rank and right rank inputs that replace the rank input in LabVIEW 8.0. This VI applies a median filter of rank to the input sequence X, where rank is right rank if right rank is greater than zero, or left rank if right rank is less than zero.
Note  If you open a LabVIEW 8.0 or earlier VI that includes the Median Filter VI with a value wired to the rank input, LabVIEW uses that value for left rank in LabVIEW 8.2.

Sound VIs (Linux)

You must have the Open Sound System (OSS) driver to use the Sound VIs. Refer to the Important Information»Copyright book on the Contents tab of the LabVIEW Help for applicable OSS copyright information.

Note  LabVIEW probes for devices by looking for files named /dev/dsp or /dev/dspX, where X is an integer between 0 and 16. LabVIEW attempts to open each device for input and output. If LabVIEW cannot detect the sound card, check that a device file named /dev/dsp or /dev/dspX exists on the local system and that you have permission to read from and write to the device. If you moved this device to a location other than the default, LabVIEW can work with a symbolic link.

The Sound VIs on Linux include the following changes:

  • The VIs support monophonic and stereophonic sound.
  • A waveform represents sound data. You can use elements of 8-bit unsigned, 16-bit signed, or 32-bit integers signed, or single and double-precision data types to represent the Y array data. Each waveform defines one channel.
  • The format of the sound data is Pulse Code Modulated (PCM).
  • The VIs can produce continuous sound output.
  • The VIs allow for a streaming view of wave files.
  • The VIs have improvements to error checking.

String Functions

The String palette includes the following changed functions:

VISA Functions

When you right-click terminals of certain VISA functions and select Create»Constant, Create»Control, or Create»Indicator from the shortcut menu, a ring object appears. The object appears as a pull-down menu that you can cycle through to make selections. All values that LabVIEW supports appear in the pull-down menus.

This change affects the following functions and terminals.

Function Terminal(s)
VISA Assert Interrupt Signal mode
VISA Assert Trigger protocol
VISA Assert Utility Signal bus signal
VISA Disable Event event type
VISA Discard Events event type
VISA Enable Event event type
VISA Find Resource search mode
VISA GPIB Control ATN mode
VISA GPIB Control REN mode
VISA Map Trigger trigger source, trigger destination
VISA Open access mode
VISA Unmap Trigger trigger source, trigger destination
VISA VXI Cmd or Query mode
VISA Wait on Event event type in, event type out

Call Library Function Node

The Call Library Function Node includes error terminals. The Call Library Function dialog box also includes the following changes:

  • The dialog box includes multiple pages, which you can use to configure parameters more easily.
  • On the Function page, you can configure the node to allow you to specify the library path programmatically by placing a checkmark in the Specify path on diagram checkbox.
  • On the Parameters page, when you configure string or array parameters, you can use the Minimum size text box to allocate memory correctly.
  • On the Callbacks page, you can specify user-defined callbacks.

Miscellaneous VI, Function, and Node Changes

LabVIEW 8.2 includes the following miscellaneous VI, function, and node changes:

  • The Mathematical Operation options in the configuration dialog box of the Time Domain Math Express VI changed from Differential to Derivative (dX/dt), from Difference to Difference (dX), from Integral to Integral (Sum[Xdt]), and from Summation to Summation (Sum[X]).
  • Windows The refnum in input of the Sound File Info (refnum) instance of the Sound File Info VI changed to sound file refnum.
  • Mac OS, Linux The Set Report Footer Text VI generates footers in a slightly different size than in previous versions of LabVIEW. The Set Report Footer Text VI also includes a new HTML footer size input.
  • The Synchronize Timed Structure Starts VI includes a clear input that removes all timed structures and deletes the entire group before adding the timed structures you specify to the group. Use this input to remove any timed structures that do not correspond to a Timed Loop. This VI also includes a timed structures names out output that returns the names of all timed structures in the group after LabVIEW adds the names to the synchronization group.
  • Windows In LabVIEW 8.0, the List Folder function appends .* to the pattern input if pattern does not already include an extension. In LabVIEW 8.2, the function does not alter the pattern input, but it appends . to the filename if the filename does not have an extension but pattern does have an extension.
  • After you place the Static VI Reference function on a block diagram, double-click the function to display a file dialog box where you can select a VI. In LabVIEW 8.0, double-clicking the function displayed a missing file error dialog box.
  • The format string input of the Format Into File, Format Into String, Scan From File, and Scan From String functions is no longer a required input.
  • Opening a VI containing a Shared Variable node in a project where the Shared Variable node cannot find its associated shared variable in the Project Explorer window causes the Shared Variable node to break. Any front panel controls associated with the missing shared variable also break. This behavior is specific to Windows, and only occurs when you open the VI node in a project. If you open the VI in the main application instance, you do not receive notification of missing shared variables. Previous versions of LabVIEW did not indicate that the Shared Variable node could not find its associate variables in the Project Explorer window.
  • In LabVIEW 8.0.1, the Wakeup Reason output of the Timed Loop is a ring. In LabVIEW 8.2, the output is an enumerated type, which is consistent with LabVIEW 8.0 behavior.
  • The names of the duplicate outputs of the following VIs and functions changed from dup [output] to [output] out. This change does not impact the functionality of these VIs and functions:

New Properties, Methods, and Events

LabVIEW 8.2 includes new VI server classes, properties, methods, and events. Refer to the LabVIEW 8.2 Features and Changes»New VI Server Classes, Properties, Methods, and Events book on the Contents tab of the LabVIEW Help for a list of new class, properties, methods, and events.

LabVIEW 8.2 also includes the following new VISA properties: PXI/PCI Settings:Is PCI Express, PXI/PCI Settings:Maximum Link Width, PXI/PCI Settings:Actual Link Width, PXI/PCI Settings:Slot Link Width, PXI/PCI Settings:D-Star Bus Number, and PXI/PCI Settings:D-Star Set.

LabVIEW MathScript Enhancements

Refer to the Fundamentals»Formulas and Equations book on the Contents tab in the LabVIEW Help for more information about LabVIEW MathScript.

LabVIEW 8.2 introduces the following enhancements and changes to MathScript.

New MathScript Functions

LabVIEW 8.2 includes the following new MathScript functions. You can use these functions in the LabVIEW MathScript Window or the MathScript Node.

  • plots class: area, bar, bar3, bar3h, barh, contour, contour3, contourf, errorbar, ezcontour, ezcontourf, ezmesh, ezmeshc, ezplot, ezplot3, ezpolar, ezsurf, ezsurfc, feather, fill, fplot, gplot, meshc, pie, plotmatrix, plotyy, polar, quiver, scatter, scatter3, shg, stem3, strips, surfc, treeplot, and waterfall.
  • dsp class: ac2poly, ac2rc, arburg, arcov, armcov, aryule, barthannwin, bartlett, besselap, besself, bilinear, bitrevorder, blackman, blackmanharris, bohmanwin, buttap, cceps, cheb1ap, cheb2ap, chebwin, chirp, conv2, convmtx, corrmtx, czt, dct, dftmtx, digitrevorder, diric, downsample, dst, ellipap, eqtflength, filternorm, filtic, firgauss, firrcos, flattopwin, freqspace, gauspuls, gausswin, gmonopuls, goertzel, hann, icceps, iczt, idct, idst, impinvar, intfilt, invfreqs, invfreqz, is2rc, kaiserord, lar2rc, latc2tf, levinson, lp2bp, lp2bs, lp2hp, lp2lp, lpc, lsf2poly, maxflat, medfilt1, nuttallwin, parzenwin, phasedelay, phasez, poly2ac, poly2lsf, poly2rc, polyscale, polystab, prony, pulstran, rc2ac, rc2is, rc2lar, rc2poly, rceps, rectpuls, rectwin, resample, residuez, rlevinson, schurrc, seqperiod, sgolay, sgolayfilt, sinc, sos2ss, sos2tf, sos2zp, sosfilt, spline, ss2sos, ss2tf, ss2zp, stepz, stmcb, tf2latc, tf2sos, tf2ss, tf2zp, tf2zpk, triang, tripuls, tukeywin, udecode, uencode, upfirdn, upsample, vco, xcorr, xcorr2, xcov, zerophase, zp2sos, zp2ss, and zp2tf.
  • support class: csvread, csvwrite, dlmread, dlmwrite, labviewroot, type, uiload, and what.
  • string class: eval.
  • libraries class: loadlibrary, calllib, unloadlibrary, libisloaded, and libfunctionsview. You can use these functions to call shared libraries from the LabVIEW MathScript Window or the MathScript Node. Refer to the MathScript Shared Libraries.lvproj in the labview\examples\MathScript\MathScript Shared Libraries directory for examples of calling shared libraries from MathScript.

Miscellaneous MathScript Enhancements and Changes

LabVIEW 8.2 includes the following miscellaneous changes to MathScript:

  • Overall performance improved in the LabVIEW MathScript Window. Compile time improved in the MathScript Node.
  • When you call the MathScript help command, LabVIEW displays help in an HTML Help window. To display help in the Output Window of the LabVIEW MathScript Window, select File»MathScript Preferences and remove the checkmark from the Display HTML Help? checkbox. If you define a function, LabVIEW always displays the help for the function you defined in the Output Window.
  • The MathScript Node behaves differently than other script nodes when you wire an unsupported data type to an input terminal. On a MathScript Node, LabVIEW either converts the data type to a supported type or displays a broken wire. If LabVIEW converts the data type, a coercion dot appears on the terminal where the conversion takes place. After you wire an input to a MathScript Node, right-click the input terminal and select Show Data Type from the shortcut menu to see the data type of the input.
  • MathScript supports all non-Unicode characters in text strings but not in variable names. You can use only ASCII characters in variable names. For example, you can use á in a text string, but you cannot call the following script from the LabVIEW MathScript Window or the MathScript Node:

    á=rand(50, 1)

    plot(á)

    You can save data to paths that contain non-Unicode characters. Also, if you install LabVIEW in a directory whose path contains any non-Unicode characters, MathScript functions correctly.
  • LabVIEW uses short-circuit evaluation to evaluate compound logical expressions in MathScript. For example, if you execute the command if 0 == 0 || foo(a) == 2, LabVIEW does not execute foo(a) because the first part of the expression already is TRUE. Similarly, if you execute the command if 0 ~= 0 && foo(a) == 2, LabVIEW does not execute foo(a) because the first part of the expression already is FALSE.

    Because LabVIEW 8.0 evaluates all parts of compound logical expressions in MathScript regardless of whether the expressions are TRUE or FALSE, LabVIEW 8.0 scripts that contain compound logical expressions might not run as expected in LabVIEW 8.2. For example, because LabVIEW 8.0 executes foo(a) in the command if 0 == 0 || foo(a) == 2, you can use the result of foo(a) to define a variable in a script. This same script executes differently in LabVIEW 8.2. Because LabVIEW 8.2 does not execute foo(a) in the command if 0 == 0 || foo(a) == 2, you cannot use the result of foo(a) in a script. If you do not want LabVIEW to use short-circuit evaluation, remove compound logical expressions from existing code.
  • MathScript supports the nargin and nargout functions within user-defined functions.
  • MathScript supports the return keyword. MathScript also supports the end keyword in matrix indexing.
  • The prod and sum functions include a b input that you can use to specify the dimension along which to compute the product or sum.

3D Picture Control

Refer to the Fundamentals»Graphics and Sound VIs book on the Contents tab in the LabVIEW Help for more information about the 3D picture control.

The 3D Picture Control VIs, properties, and methods convert a collection of 3D objects into a 3D scene that you can view and manipulate. You can generate multiple 3D objects and specify their size, shape, movement, appearance, and relationship to other objects within the scene.

Use the following VIs, properties, and methods to specify the appearance of a 3D object:

  • Use the Object VIs to create or find 3D objects. You also can use the SceneObject properties and SceneObject methods to place 3D objects in the scene and assign the objects characteristics programmatically.
  • Use the File Loading VIs to add existing model or scene files to the 3D scene.
  • Use the Geometries VIs with the SceneGeometry properties and SceneGeometry methods to specify the geometric form a 3D object takes.
  • Use the Transformations VIs to position objects in a 3D scene.

Use the Helpers VIs to perform common 3D scene operations. You can configure a separate window for the scene, create new clip planes within the scene, add light sources, apply textures to 3D objects, and convert LabVIEW color values to appear in the 3D picture control.

You also can use the following properties and methods to configure a 3D scene programmatically:

  • Use the SceneWindow properties to render the scene in a separate window, configure the window, and set the interaction of the camera controller with the scene.
  • Use the SceneClipPlane properties to specify planes in the scene in which an object appears or is cut off.
  • Use the SceneLight properties to configure a light source for the scene.
  • Use the SceneTexture properties and SceneTexture methods to apply textures to a 3D object.

Refer to the solarsystem VI in the labview\examples\picture\3D Picture Control directory for an example of creating a 3D scene with the 3D picture control.

LabVIEW Object-Oriented Programming

Refer to the Fundamentals»LabVIEW Object-Oriented Programming book on the Contents tab in the LabVIEW Help for more information about object-oriented programming in LabVIEW.

LabVIEW object-oriented programming uses concepts from other object-oriented programming languages such as C++ and Java, including class structure, encapsulation, and inheritance. You can use these concepts to create code that is easier to maintain and modify without affecting other sections of code within the application. You can use object-oriented programming in LabVIEW to create user-defined data types.

Creating LabVIEW Classes

You create user-defined data types in LabVIEW by creating LabVIEW classes. LabVIEW classes define data associated with an object, as well as the methods that define the actions you can perform on the data.

In LabVIEW, the data of a class is private, which means only VIs that are members of the class can access the data. You define the data of the class in the private data control. When you create and save a LabVIEW class, LabVIEW creates a class library file (.lvclass) that defines a new data type. The class library file records the private data control and information about any member VIs you create, such as a list of the VIs and various properties of the VIs. The class library is similar to the project library (.lvlib). However, the class library defines a new data type.

Defining Private Data Controls

LabVIEW creates a private data control of the class automatically when you create a LabVIEW class.

You use the Control Editor window to customize the private data control of a class. LabVIEW displays the Control Editor window when you double-click the private data control of the class in the Project Explorer window. You can place controls and indicators in the Cluster of class private data to define the private data type of a LabVIEW class. The default values you set for the controls in the Cluster of class private data are the default values for the class.

Creating Member VIs

Member VIs implement the methods you create for the LabVIEW class. You create member VIs to perform operations on the private data of the class. Member VIs are members of the LabVIEW class in which you create them and appear in the Project Explorer window under the private data control of the class. You can define most methods using a single member VI in one class, but some methods you might define by creating multiple member VIs throughout the class hierarchy.

Distributing a LabVIEW Class to Other Developers and Users

You can distribute the LabVIEW class you develop to other LabVIEW class developers and LabVIEW class users. You can distribute the class in several ways so choose the manner that most suits your needs. You can use the Application Builder to create a zip file to distribute the class or classes. You also can lock the LabVIEW class before you distribute it to limit the access the LabVIEW class user has to the private data and member VIs. Locking the class can help prevent users from introducing errors in the application.

LabVIEW Project Enhancements

LabVIEW 8.2 includes the following enhancements to the LabVIEW project and related functionality:

Application Builder Enhancements

LabVIEW 8.2 includes the following enhancements to the Application Builder in the LabVIEW Professional Development System:

  • Automatically incrementing product version—If you build an installer multiple times, LabVIEW can increment the product version number automatically for each new version of the installer. The Auto increment product version checkbox appears on the Product Information page of the Installer Properties dialog box.
  • Specifying media size for storing the installer—You can customize media size when saving installer components. The Enable media spanning checkbox appears on the Advanced page of the Installer Properties dialog box. The pull-down menu of media includes a Custom option. Use this option to enter an arbitrary media size value in the Media size (MB) text box.
  • Requiring Windows 2000 or later—You can require that users have Microsoft Windows 2000 Service Pack 3 or a later version to run the installer. The Windows 2000 or later option appears in the System Requirements section of the Advanced page of the Installer Properties dialog box.
  • Caching installer components—If you build an installer more than once and the installer contains additional installers or components, caching eliminates the need to specify a location for the additional components each time you build the installer.

    The first time you build the installer, the Locate Distribution dialog box prompts you to locate the distribution that contains the additional components. Place a checkmark in the Cache component from this distribution checkbox to copy files from the distribution into a permanent location on the local system. The next time you build an installer that includes these components, the Application Builder automatically copies the components from the local system instead of prompting you for a distribution CD.
  • Dynamic VIs and dependencies—If a VI specified as a dynamic VI on the Source File Settings (Application) page is going to a destination other than the built application, Application Builder moves all dependencies of the dynamic VI to the new destination with the dynamic VI, rather than keep the dependencies in the built application. If two or more dynamic or top-level VIs call a VI and try to move it to two different locations, Application Builder moves the VI and all subVIs to the built application. To make a VI that is specified as Include only if referenced on the Source File Settings page move to a new location, you must specify the VI as a dynamic VI.
  • Using project alias files with shared libraries—The Advanced page of the Shared Library Properties dialog box includes the Use the default project alias file checkbox, which associates the project alias file with the shared library. If you remove the checkmark from the checkbox, specify an alias file to use in the Alias file in project textbox.
  • Including additional LabVIEW header files with shared libraries—The Advanced page of the Shared Library Properties dialog box includes the Include additional LabVIEW header files checkbox, which copies any additional LabVIEW header files that the header file, generated during the builder process, references. You can include additional header files to use a LabVIEW built shared library in C or another language that requires those header files.
  • The New Destination button on the Distribution Settings page of the Source Distribution dialog box changed to the Add button. Also, all options related to excluding files from a source distribution moved to the Additional Exclusions page.
  • The New Destination button on the Destinations page of the Application Properties dialog box and Shared Library Properties dialog box changed to the Add button.
  • You can build an application or source distribution without saving VIs first.
  • If you do not add the .zip extension to zip files you create in the Application Builder, LabVIEW adds the extension automatically.

New Dialog Box Pages

LabVIEW 8.2 includes the following new Application Builder dialog box pages:

  • Installer Properties dialog box
    • Dialog Information—Use the this page to design the user interface for the installer. You can set the language for the text, display a custom readme and license agreement, and set a welcome title and message. This page replaces the Dialog information section on the Product Information page in LabVIEW 8.0.
      Note  The Include custom license agreement option of the Dialog Information page replaces the License file option which appeared on the Product Information page.
    • Hardware Configuration—Use the this page to specify the source of hardware configuration information to include in the installer. The new Import Mode section includes more options for importing hardware configuration files from Measurement & Automation Explorer. This page replaces the Hardware configuration section of the Advanced page in LabVIEW 8.0.
  • Application Properties, Shared Library Properties, and Source Distribution Properties dialog boxes
    • Additional Exclusions—Use this page to configure settings for removing or disconnecting type definitions, unused polymorphic VI instances, and unreferenced members of project libraries. Use these settings to reduce the size of the build.

Duplicating and Rearranging Build Specifications

You can duplicate build specifications in the Project Explorer window. Right-click the build specification to duplicate and select Duplicate from the shortcut menu to create a copy of the build specifications under the Build Specifications.

You also can drag and drop build specification items to rearrange the build order within the same Build Specification.

Activating the Application Builder (Windows)

If you have an activated version of the LabVIEW Base Package or Full Development System, you can select Help»Activate Application Builder to activate the Application Builder. The license takes effect when you restart LabVIEW.

Creating Project Libraries and Adding Shared Variables Programmatically

Use the CreateOrAddLibrary VI in the labview\vi.lib\Utility\Variable directory to add a library to a project or a parent item such as a target, folder, or another library programmatically.

You also can use the AddSharedVariableToLibrary VI in the labview\vi.lib\Utility\Variable directory to add shared variables to a library programmatically.

Saving LabVIEW Projects and Project Libraries for a Previous Version

You can save LabVIEW projects and project libraries that are readable by LabVIEW 8.0. To save a LabVIEW project for a previous version, select File»Save for Previous Version in the Project Explorer window. To save a project library for a previous version, right-click the library file in the Project Explorer window and select Save For Previous Version from the shortcut menu, or open the project library and select File»Save for Previous Version.

Selecting an Application Instance

LabVIEW creates an application instance for each target in a LabVIEW project. When you open a VI from the Project Explorer window, the VI opens in the application instance for the target. LabVIEW also creates a main application instance, which contains open VIs that are not part of a project and VIs that you did not open from a project. You can open VIs in a specific application instance by using the application instance shortcut menu. Right-click the current instance name in the bottom left corner of the front panel window or block diagram window to display the shortcut menu and select among all application instances. Selecting a new application instance reopens the VI in the selected application instance. The VI also remains open in the original application instance.

Shared Variable Enhancements

LabVIEW 8.2 includes the following shared variable enhancements:

  • LabVIEW uses the Network:BuffSize, Network:ElemSize, and Network:PointsPerWaveform properties as appropriate to calculate the network buffer size for a network-published shared variable.
    • For scalar network-published shared variables, LabVIEW uses the Network:BuffSize property, which indicates the number of values to buffer.
    • For array and string network-published shared variables, LabVIEW uses the Network:BuffSize and Network:ElemSize properties.
    • For waveform network-published shared variables, LabVIEW uses the Network:BuffSize and Network:PointsPerWaveform properties.
    • For array of waveform network-published shared variables, LabVIEW uses the Network:BuffSize, Network:ElemSize, and Network:PointsPerWaveform properties.
  • The variable input of the Shared Variable node is required when the node is configured to write data.
  • The Variable page of the Shared Variable Properties included the following changes:
    • The Custom item in the Data Type pull-down menu changed to From Custom Control.
    • The Data Type pull-down menu includes a new Variant item.
    • No longer displays the element size for the network buffer.
    • If you set Access Type to read only or write only, you can create shared variables that are configured only to read data or write data, respectively. When you right-click the shared variable that is bound to a source that is read or write only, LabVIEW disables the Change to Write and Change to Read options in the shortcut menu.
    • In LabVIEW 8.0, you right-click the Shared Variable node and select Show timestamp from the shortcut menu to obtain time stamp information about the single-process shared variable. In LabVIEW 8.2, you must first right-click the shared variable in a project, select Properties from the shortcut menu, and place a checkmark in the Enable timestamp checkbox on the Variable page to obtain time stamp information about the single-process shared variable. To view the time stamp information and add a timestamp output to the Shared Variable node, right-click the Shared Variable node and select Show Timestamp from the shortcut menu. If you load a single-process shared variable in LabVIEW 8.2 that you created in LabVIEW 8.0, the time stamp is enabled by default.
  • In LabVIEW 8.0, LabVIEW dims items you cannot select in the list of the Select Variable dialog box. In LabVIEW 8.2, LabVIEW dims the OK button if you select an invalid item from the list.

Miscellaneous Project Enhancements

LabVIEW 8.2 includes the following miscellaneous project enhancements:

  • In LabVIEW 8.0, if you create a type definition in a project library and set the access scope of the type definition as private, you still can reference the private type definition in a VI outside the project library. In LabVIEW 8.2, you cannot reference private type definitions outside of the library.
  • Right-click an XControl and select New»VI from the shortcut menu to create a VI inside an XControl.
  • In LabVIEW 8.0, you have to save an XControl ability, property, or method VI after you set a breakpoint when debugging. In LabVIEW 8.2, you no longer have to save abilities, properties, or method VIs after you set breakpoints.
  • When you enter a password for a library in a LabVIEW project that does not have a valid license specific to the version of LabVIEW you purchased, you cannot drag and drop items into or out of the library.
  • If a project library is password protected and the password is not in the LabVIEW password cache, you can right-click the project library and select Enter Password from the shortcut menu to unlock the project library.

Controlling VIs Remotely from Multiple Clients

Multiple clients can control an application or VI remotely at the same time. To allow simultaneous control of a VI, the VI must be reentrant. To make a VI reentrant, select File»VI Properties, select Execution from the Category list, and place a checkmark in the Reentrant execution checkbox. LabVIEW opens a clone of the reentrant VI for each client request for a remote front panel. You can use the Web Server:VI Access List property to programmatically limit access to clones already in memory for remote front panel connections.

Importing Functions from a Shared Library File

You can generate and update VIs for exported functions in a Windows .dll file, a Mac OS .framework file, or a Linux .so file. Select Tools»Import»Shared Library then follow the prompts to create wrapper VIs for shared library files. You must provide the name of a shared library file and a header .h file.

Refer to the Fundamentals»Calling Code Written in Text-Based Programming Languages»How-To»Importing Functions from Shared Library Files on the Contents tab of the LabVIEW Help for more information about creating wrappers for shared library files.

Instrument Driver Templates

LabVIEW 8.2 includes the following new templates for the Create New Instrument Driver wizard:

  • General Purpose (register-based)—Use for register-based instruments for which there is no class-specific template. Common register-based instruments include: VXI and PXI.
  • Spectrum Analyzer—Controls basic operations such as setting the frequency range and sweep coupling. The template also includes advanced features such as configuring and querying the marker.

.NET and ActiveX Enhancements (Windows)

LabVIEW 8.2 introduces the following enhancements and changes to .NET and Active X.

User interface thread dependency no longer exists for .NET controls. You do not have to set a VI or subVI to run in the user interface thread for .NET control operations. By default, LabVIEW sets any .NET controls to run in the correct thread, which in most cases is the user interface thread.

LabVIEW does not support debugging in ActiveX and .NET callback VIs. If you use breakpoints in ActiveX and .NET callback VIs, LabVIEW does not pause at the breakpoint.

In LabVIEW 8.0 and earlier, the .NET Refnum Probe displayed only the hex value of the reference. In LabVIEW 8.2, the .NET Refnum Probe displays the result of calling the ToString() method on the object represented by the .NET refnum, the type of the object, the hash code of the object, and the hex value of the reference. You can use this probe to set a breakpoint if the value is an invalid refnum.

LabVIEW 8.2 includes the following changes in the .NET and ActiveX menus:

  • The Tools».NET & ActiveX menu items, Add .NET Controls to Palette and Add ActiveX Controls to Palette, changed toTools»Import».NET Controls to Palette and Tools»Import»ActiveX Controls to Palette, respectively.
  • The Tools».NET & ActiveX»Browse ActiveX Properties menu item changed to View»ActiveX Property Browser.

NI Example Finder Enhancements

The Most Recent examples folder appears on the Browse tab of the NI Example Finder by default. You can set the maximum number of examples to display in the Most Recent examples folder by clicking the Setup button in the NI Example Finder and clicking the General tab.

Refer to the NI Example Finder Help for more information about enhancements to the NI Example Finder. Click the Help button in the NI Example Finder to display the NI Example Finder Help.

Source Control Enhancements

Refer to the Fundamentals»Organizing and Managing a Project book on the Contents tab in the LabVIEW Help for more information about source control in LabVIEW.

The following third-party source control providers have been tested for integration and basic functionality with the LabVIEW 8.2 Professional Development System:

  • Seapine Surround SCM
  • Borland StarTeam
  • Telelogic Synergy
  • PushOK (CVS and SVN plugins)
  • ionForge Evolution
Note  Currently, ionForge Evolution 2.8 and later works with LabVIEW.

Also, additional third-party source control providers are compatible with the procedure LabVIEW uses to complete a graphical differencing of VIs than were compatible with LabVIEW 8.0.

Source Control Operations on LabVIEW Project Folders

You can perform source control operations on a folder of items in a LabVIEW project. LabVIEW performs the operation on all appropriate items within the hierarchy. For example, if you add files to source control, LabVIEW adds only files within the folder that you have not yet added to source control. When you perform source control operations on a folder of items, all source control configuration options that apply to any of the folder items appear.

Note   If you have a project library within a folder, the source control operations you perform do not extend to items within the project library. To perform source control operations on items within a project library, you must select the items manually. You can perform source control operations on a folder within a project library.

Unsaved Files in Source Control Operations

If you attempt check-in operations on files that contain unsaved changes, the Unsaved Files dialog box prompts you to save or ignore the changes. This dialog box appears if you click the OK button in the Source Control Operations dialog box and a LabVIEW file type included in the source control operation has unsaved changes. This dialog box also appears if you select Tools»Source Control»Show Differences in a library or project file that has unsaved changes.

Miscellaneous Source Control Enhancements

LabVIEW 8.2 includes the following miscellaneous source control enhancements:

  • In LabVIEW 8.0, the Add to Source Control menu item is available for unsaved files in the Tools»Source Control menu. In LabVIEW 8.2, the Add to Source Control menu item is not available until you save the file.
  • Select Tools»Source Control»Configure Source Control and use the Exclude vi.lib and Exclude instr.lib checkboxes to exclude files in the vi.lib and instr.lib directories when adding files to source control. If you configure LabVIEW to include dependencies when adding files to source control, these options exclude unnecessary files from the operation.
  • The Perforce Revision History dialog box includes the options Sync to this revision and Describe changelist. To access these options, right-click a revision in the History list.
  • In the Perforce Revision History dialog box, the Actions in changelist field displays actions taken in the current changelist. Possible operations include add, edit, delete, branch, and integrate. This field also displays the type of file on which the action occurs.
  • Windows If you install the Perforce core installer, Perforce SCM appears in the Source Control Provider Name pull-down menu of the Source Control page of the Options dialog box.

TDM Enhancements

LabVIEW 8.2 includes the following TDM enhancements.

TDM Streaming File Format

LabVIEW 8.2 includes the TDM Streaming (.tdms) file format for storing binary data. The .tdms file format provides faster writing performance than the .tdm file format available in LabVIEW 8.0 and earlier. The .tdms file format also provides a simpler interface for defining properties.

Refer to the TDM Streaming VIs and Functions section of this document for information about TDMS VIs and functions.

User-Defined TDM and TDMS Properties

You can create and customize user-defined properties and specify DAQmx properties for binary measurement files. Use the Write To Measurement File, Write Data, Set Properties, and Get Properties Express VIs to configure user-defined properties for .tdm or .tdms files.

Click the Advanced button in the Write To Measurement File Express VI configuration page to configure properties. Display the configuration page of the Write Data, Set Properties, and the Get Properties Express VIs to configure properties.

Importing Web Services (Windows)

You can use Web services in LabVIEW 8.2 without managing all the complexities behind Web services. You can transform any Web service into a project library of VIs that you then can use to program the Web service as if it were independently available on the local computer. You must provide a valid URL to a Web Service Description Language (WSDL). WSDL is an XML-formatted language used to describe a Web service and its functionality. Select Tools»Import»Web Service to launch a wizard that guides you through the process of importing the methods in a Web service and creating a library of VIs.

Note  You must have the .NET Framework, version 1.1 or later, installed to use the Import Web Service wizard.

Refer to the Fundamentals»Windows Connectivity»Concepts»Importing Web Services book on the Contents tab in the LabVIEW Help for more information about importing Web services.

External Code Functions Changes

The data type size_t replaces type int32 in certain places in the Memory Manager interface for use by external source code. This change is compatible with existing DLLs.

Refer to the Memory Manager Functions topic in the LabVIEW Help for more information about the Memory Manager functions.


Resources


 

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit