LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Nate@UT

Value Change event: was it generated due to Front Panel change or Val(Sgnl) property node write?

Status: New

Suggest adding functionality to the event structure when handling Value Change events, so that the user can tell whether the source of that generated event was via a write to a Val(Sgnl) property node, or via a Front Panel change made by the user. 

 

This could potentially be achieved (albeit with backwards compatibility considerations) by defining an appropriate enum constant for the eventsource.ctl which available in the "Source" field of the Event Data Node (currently has "LabVIEW UI, ActiveX, User Event, and Other <>..." as the only defined constants).

 

More discussion and rationale is in this community topic:

Solved: Re: UI-Triggered Event vs. Value (Signaling) Event? - NI Community

2 Comments
wiebe@CARYA
Knight of NI

(Sorry) Duplicate: Expand the Source value of events to include Value (Signaling) - NI Community

 

I suggest (it's not up to me) we keep the new idea open for now: maybe it gets some traction now. 

 

It would actually give "Source" a some purpose. I don't recall ever using "Source"; I do recall looking at it expecting it to distinguish between a value (signaling) and UI event. It might be a code smell if you need it though, as implied by @mads' comment.

Nate@UT
Member

Thank you @wiebe for pointing out the duplicate from 15 years ago (!) -- that didn't come up when I searched originally but describes the same concept.

 

As discussed in the linked community topic, there is a need for this functionality which cannot be achieved elegantly (or even at all?) using UEs but can be achieved with a variant-typed Val(Sngl) property node, so I argue this this puts it outside the realm of a code-smell and into something which has real value. 

 

https://forums.ni.com/t5/LabVIEW/UI-Triggered-Event-vs-Value-Signaling-Event/m-p/4432639