|VI Server Property Information
||All Supported Methods
|* Displayed here in English. Short and Long names appear in the language of the LabVIEW IDE.
|Owning Class ID
|Owning Class Name
||Common Cluster Array data type
|Available in Real-Time Operating System||No|
|Available in Run-Time Engine||No|
|Loads the block diagram into memory||Yes|
|Loads the front panel into memory||Yes|
|Need to authenticate before use||No|
|Remote access allowed||Yes|
|Settable when the VI is running||No|
Lists all methods supported for the current class.
Some methods have a Unique ID string. The Unique ID string is consistent across all versions and locales of LabVIEW. Methods without a Unique ID string return an empty string. All methods return Data name, Short name (localized), and Long name (localized), which contain the strings shown to the user in this version and locale of LabVIEW; however, strings can vary across versions, locales, and even individual launches of LabVIEW.
Programmatic Access to All Methods
Through VI Scripting the all of the methods of a given class can be seen by accessing the All Supported Methods property of the Invoke class. Start by setting the invoke node to the desired class. Then, through scripting functions, get the reference to that invoke node and read the All Supported Methods property of it. It will return an array of clusters with each element of the array representing an acceptable method of the given class or of a class in its inheritance chain. The cluster contains the following for elements about the method:
- Unique ID string - This is a unique ID for the method
- Data Name - This is the data name of the method
- Short Name (localized) - This is the name of the method as it would appear in a invoke node in the language of the LabVIEW IDE
- Long Name (localized) - This is the name of the method as it would appear in a drop-down menus as the method was being selected and is in the language of the LabVIEW IDE
||More info to come.