VIs Strings:Export Method
Short Name: VIs Strings.Export
Installed With: Base Package
Class: Application Methods
Exports to a tagged text file all the User Interface related strings of the VIs specified by VI Array.
Exports the following strings about VI and front panel objects to a tagged text file: VI name and description, object caption labels, object free labels, default data (string, table, path, and array default data), private data (listbox item names, table row and column headers, graph plot names, graph cursor names, graph annotation names, and tab control page captions), and polymorphic VI data (instance names in the polymorphic VI and selector shortcut menus).
Parameters
| Name | Required | Description |
|---|---|---|
| VI Ref Array | No | Path to an array of VI references. |
| String File | No | Path of the VI strings file, including the filename. If you do not enter a filename, make sure to set Interactive to TRUE so the user can set the VI strings filename. |
| Interactive | No | Specifies whether to display the file dialog box to select the name of the VI strings file. The default value is FALSE. |
| Log File | No | Path of the log file created to list errors that occurred while exporting VI strings to a tagged text file. The default value is no logging. |
| Create Captions | No | Specifies whether control captions should be automatically created. The default value is FALSE. |
| Export Diagram | No | Specifies whether to export block diagram strings. The default value is FALSE. |
| Error Array | No | Returns an array of error clusters. |
Remarks
The following table lists the characteristics of this method.
| Available in Run-Time Engine and Real-Time Operating System | No |
| Settable when the VI is running | No |
| Loads the front panel into memory | Yes |
| Need to authenticate before use | No |
| Loads the block diagram into memory | No |
| Remote access disallowed | No |
| Must wait until user interface is idle | Yes |
| Available with control VIs | Yes |
| Available with global VIs | Yes |
| Available with strict type definitions | No |
| Available with polymorphic VIs | Yes |