How to add a Property Node with 'Disabled(U8)

[LittleBigPig]

Anyone can tell me how to add a Property Node with 'Disabled(U8)'? Thanks.

[GerdW]

Hi BigPig,

use a "standard" "Disabled" property. No need to use that old (deprecated) "Disabled (U8)" anymore!

[RavensFan]

We can't read Chinese.  What does the label say?

What object is the property node associated with?  Where did you get this image from?

The pink in the header means it is a special property node.  I might be wrong, but pink might mean it is an obsolete property.

[JÞB]

---

@RavensFan wrote:

We can't read Chinese.  What does the label say?

What object is the property node associated with?  Where did you get this image from?

The pink in the header means it is a special property node.  I might be wrong, but pink might mean it is an obsolete property.

---

You are right.  The Disabled property value was changed from a U8 to a type def Enum <Enabled, Disabled, Disabled and Greyed > so many versions back that it would take an archeologist to dig up the release notes.

[Kyle97330 · Accepted solution]

Like everyone else says, you almost certainly don't NEED this node, and using a standard "Disabled" node should work just fine.

However, just as a general note, if there's a hidden property on any node, no matter why it's hidden (deprecated, scripting, developer mode, etc.) this should always work to create it:

1. Create a property or invoke node from the object type you want the hidden property of.  In this case, it appears to be a numeric property node.

2. Select the node (and nothing else), then press control-space to bring up the quickdrop window.

3. In the quickdrop window, type in the exact name of the property or function you need (case insensitive, but spacing and punctuation needs to be intact).

4. Press Control-Shift-B.

I was able to create this in LabVIEW 2018 by doing this.  I don't know if there could possibly be any legitimate purpose to do this for this exact node, but there you go...

[JÞB]

Kyle 

Thanks,  I did not know that!  Do the Forums a favor and drop this tidbit into the micro-Nuggets thread.

https://forums.ni.com/t5/LabVIEW/Micro-Nuggets-Post-em-if-you-got-em/td-p/1276066 

[RavensFan]

Interesting idea,  but this did not work for me.

When I followed the steps, I got the property node replaced with a VISA Disable Event.

It seems like there might be some other settings that allows a hierarchy of properties to be items within the quick drop window.

Others try Kyle's instructions.  Let us know if it did or didn't work for you.

[GerdW]

Hi RavensFan,

it worked for me.

(I had to use the German name of the "Deaktiviert (U8)" property to make it work. Next time I install LabVIEW I will definitely take care of installing the English version again…)

[LittleBigPig]

Kyle, 

This did not work for me in LabVIEW2019. 

I try to create a Property Node of ‘Slope and intercept’ - 'Disabled' to replace the ‘Disabled(U8)’ , there is some wrong here.

[RavensFan · Accepted solution]

Your problem is the Fit Model control is an enum with the values of Linear, Polynomial and spline.  It is being coerced into a U8 with the deprecated Disabled (U8) property node.  So with the coercion, it seems to work.

Then you proceed to coerce that to an I32 when you add a 2 to it.  Then with a coercion to the valid Disabled property nodes which are enums of Enabled, Disabled,  And Disabled and Greyed Out,  all seems to work.

But you have to admin that coercing Linear, Polynomial, and Spline to the enabled/disabled conditions, makes absolutely no sense.

Get rid of the Fit Model Control, and just create constants from the Disabled property nodes using Right click >> Create Constant.   Change the Disabled (U8) property node with Disabled, then wire up a copy of the enum constant to that.

Really, all 3 of those property nodes belong outside the case structure, and the case should just determine which constants go to each one.  No playing with the Fit Model and the +2.

And Index Array is expandable.0

Here is your code cleaned up.