Ring class/Allow Undefined Values property: Difference between revisions
Added new property page. |
m Category reorg |
||
| Line 43: | Line 43: | ||
{{ambox|text=Add links to external resources that would also help.}} | {{ambox|text=Add links to external resources that would also help.}} | ||
[[Category:VI Server Property]] | |||
Latest revision as of 13:42, 7 May 2020
| VI Server Property Information | |
|---|---|
| Property ID | 633E000 |
| Scope | Basic Development Environment |
| Data Name | AllowUndefVals |
| Short Name* | AllowUndefVals |
| Long Name* | Allow Undefined Values |
| * Displayed here in English. Short and Long names appear in the language of the LabVIEW IDE. | |
| Owning Class ID | 34 |
| Owning Class Name | Ring 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 | Yes |
| Need to authenticate before use | No |
| Permissions | Read/Write |
| Remote access allowed | Yes |
| Settable when the VI is running | Yes |
If TRUE, users can enter numeric values not already associated with any entries in the list of items defined for a ring control. Users must enter undefined numeric values in the digital display of the control. If FALSE, users must select from the list of items defined for the control.
This property is similar to the Allow Undefined Values item on the shortcut menu of a ring control and the Allow undefined values at run time checkbox on the Edit Items page of the Ring Control Properties dialog box.
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. |