If you programmatically change a value on a disabled control, does it become re-enabled?

[cayenne]

I'm trying to troubleshoot a problem on an area that used to work before I added new codes....

I have a cluster with  LED booleans, Ring type dropdown menus and text boxes.

Previously...I had situations, where I disabled the whole cluster...and it worked, and I even sensed on mouse down, that someone was trying to make changes while it was disabled and I put forth a user message teling them no changes could be made.

Now..I have some code added, that will do updates on the value of the LEDs based on code coming in now from a serial connection. I"m wanting to change the value of the LEDs (and eventually the other controls on the cluster) even while it is disabled.

However, now...when I click the supposedly disabled cluster...I can now change the LED value...like it isn't disabled anymore, yet the code for the User Message still fires off.

Just to test things....I set the disabled property from 1 to 2...so it would be totally disabled and greyed out....THAT isn't happening now.....so, I'm puzzled.

My first thoughts were...that maybe LV is re-enabling parts of it when I programmatically change a value of something disabled on the front panel....is this the case?

Thank you,

cayenne

[P@Anand · Accepted solution]

In a cluster when you update the value of a disabled control it will get updated and you can read the value programatically but if the same control you try to access through the front panel manually you cannot access that similar case with the Disabled grayed out property. So you can understand the property is given to show the user that the control is in-accessable but it will not be re-enabled unless you change the disabled property of the control.