LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Mark_Yedinak

Provide a property for controls to indicate if they were wired or not

Often it is desirable to know if a control on the connector pane was wired or not. At present this can only be done by checking the value or by making the control a variant and checking if an error occurs when converting it to the proper type. Both of these have issues. Using the default value does not always work because you may need to take different action it is is truly not wired. If the control is an ENUM it would mean you have to include some value like "Invalid" in the list. This can cause confusion when using ENUM constants because it would appear that the ENUM has another value. The variant approach is problematic because it defeats automatic type checking by the compiler. It would be best if we had a simple property node on the control to indicate if it is wired or not.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
4 Comments
Darin.K
Trusted Enthusiast

Triplicate:

 

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Wired-property-node-on-controls-and-indicators/idi-p/1...

 

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/New-property-of-Method-to-indicate-if-an-input-of-a-su...

 

I have never been a real fan of this type of functionality, particularly with the File functions that give you a dialog when unwired.  If I want to know if something is wired I tend to make the connection required, then I know it is wired.

Mark_Yedinak
Trusted Enthusiast

Sorry for the duplicate post. I tried searching but obviously didn't use the right searches.

 

Anyway, I have run into an issue where this is a problem and the "invalid" value approach does not work. I have a rather complex X-Control that is configured to retain its value. I also have a dialog box which prompts the user for an input value for the X-Control. No, I'm not using the "is wired" property to determine if the dialog should be called or not. I have an input to the subVI which is the dialog box and I need to know if it is wired or not. If it is, use that as the initial value. If not, use the value from the X-Control. This comes into play since I need to know the initial value to set and the default value should be a valid setting. Therefore if I test the value of the wired input how would I know if it is wired or not since the default value is valid. Was the control wired but the default value was passed in or was it unwired?



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
AristosQueue (NI)
NI Employee (retired)

Mark:

Please read my post here for why this feature is unlikely to ever happen.

G-Money
NI Employee (retired)