Control class/Value (Signaling) property: Difference between revisions
Appearance
Added new property page. |
(No difference)
|
Revision as of 18:34, 6 April 2020
| VI Server Property Information | |
|---|---|
| Property ID | 6332023 |
| Scope | Basic Development Environment |
| Data Name | Val(Sgnl) |
| Short Name* | Val(Sgnl) |
| Long Name* | Value (Signaling) |
| * Displayed here in English. Short and Long names appear in the language of the LabVIEW IDE. | |
| Owning Class ID | 6 |
| Owning Class Name | Control Class |
| Data Type | LV Variant 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 | Write Only |
| Remote access allowed | Yes |
| Settable when the VI is running | Yes |
Sets the value of the control and generates a Value Change event.
This property updates the value of an object similar to the Value property. However, Value (Signaling) also causes LabVIEW to generate an event as if the user had interactively changed the value of the object. National Instruments recommends you use this property only when you rely on LabVIEW generating an event in response to the programmatic value change.
If this is a Boolean value configured with a latching mechanical action, this property always returns an error. Due to race conditions that can occur when you have a Boolean value with latching mechanical action, you cannot programmatically read Boolean values that are set with a latching mechanical action.
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. |