DAQmxNameConstant class/Allow Undefined Names property: Difference between revisions
Added new property page. |
m Added VI Scripting Property Category to page |
||
| (One intermediate revision by the same user not shown) | |||
| Line 42: | Line 42: | ||
== External Links == | == External Links == | ||
{{ambox|text=Add links to external resources that would also help.}} | {{ambox|text=Add links to external resources that would also help.}} | ||
[[Category:VI Scripting Property]] | |||
[[Category:VI Server Property]] | |||
Latest revision as of 19:56, 7 May 2020
| VI Server Property Information | |
|---|---|
| Property ID | 78CA7001 |
| Scope | VI Scripting |
| Data Name | AllowUndefNames |
| Short Name* | AllowUndefNames |
| Long Name* | Allow Undefined Names |
| * Displayed here in English. Short and Long names appear in the language of the LabVIEW IDE. | |
| Owning Class ID | 16457 |
| Owning Class Name | DAQmxNameConstant Class |
| Data Type | Boolean data type
|
| Property Node | 
|
| Available in Real-Time Operating System | Yes |
| Available in Run-Time Engine | Yes |
| Loads the block diagram into memory | No |
| Loads the front panel into memory | No |
| Need to authenticate before use | No |
| Permissions | Read/Write |
| Remote access allowed | Yes |
| Settable when the VI is running | Yes |
Allows undefined item names to be entered.
If TRUE, you can enter any string into the I/O name control.
Uses
 |
Specific use cases for this property. |
History
| |
History information is needed. What changes have occurred over previous versions? |
| Version | Change(s) |
|---|---|
|
More info to come. |
See Also
| |
Add links to internal wiki pages that would also help. |
External Links
| |
Add links to external resources that would also help. |