LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
Steen S. Schmidt

Wired? property node on controls and indicators

Status: Duplicate

I propose a property node to tell if a control was wired when This VI was called as a subVI.

 

Wired.png

 

Sometimes it is practical to be able to distinguish if the value in a control was wired to it (data arrived via dataflow), or if the control was unwired and the value hence the control's default value. Even comparison with the known default value of the control isn't enough, as the program logic may depend on the value source.

 

Consider an FG that stores two data elements:

 

FG.png

 

You'll have to have two Set functions for this, one for Data 1 ("Set data 1"), and one for Data 2 ("Set data 2"). If you have only one Set function, you add the constraint that both data sets have to be present (wired) every time you set any of the two data sets, or else the unwired set will get overwritten in the FG with the default value of the unwired control. If the FG could decide programmatically if the value was wired to the control, or if it was merely the default value of the unwired control, it could decide whether to overwrite its stored copy or not. The data values could be the same in the two cases, but the actions very different. This is just a simple example, but I have many much more complex cases, that would get much simpler if I could tell where the control value came from. In the above example you could even dispose of the Function input alltogether, if I could tell if any data inputs were wired.

 

A polymorphic VI will remedy some of these issues, but not all, and in other cases a polymorphic VI is a drastic solution to a simple problem. It's also not an issue in a Top-level VI, as such run only once (only subVIs get called again and again, while depending on prior runs).

CLA and CTA. Worked with LabVIEW from 4.0 to 2010 and counting...
4 Comments
tst
Knight of NI Knight of NI
Knight of NI

Duplicate (and look at the comments there) - http://forums.ni.com/t5/LabVIEW-Idea-Exchange/New-property-of-Method-to-indicate-if-an-input-of-a-su...


___________________
Try to take over the world!
Laura F.
Active Participant
Status changed to: Duplicate
 
Steen S. Schmidt
Member

Shouldn't status on the other duplicate idea (1½ years old) be changed to "declined" then?

CLA and CTA. Worked with LabVIEW from 4.0 to 2010 and counting...
AristosQueue (NI)
NI Employee (retired)

> Shouldn't status on the other duplicate idea (1½ years old) be changed to "declined" then?

 

You'll notice that no idea has been declined yet. There's a pretty strong debate internally about the process for formally and finally declining an idea. When we launched the Exchange, we had one idea for how that would work, but we don't like that process now, so a new one is being plotted, but some of the folks who need to be involved there are just a bit distracted with the next LV release. My guess is that we'll start declining ideas just before NI Week this year, but that's not official.