Boolean Control, Can I disable/gray equivalent to being locked ?

[winterishere8]

All
I want to disable a boolean control based on prior specification. When I try to use the disable/gray feature, it does not stop the user from using the button. Disable/gray only affect the button visually. Is there a way that I can lock/unlock the boolen control usage so the user can only use it when i unlock ?

[Darren]

Disabling and Graying out a boolean control should prevent user interaction of that control on the front panel.  It sounds like something may be awry in your VI.  Can you post a simple VI demonstrating the problem?

-D

[nyc_(is_out_of_here)]

Hmmmm.

I just tried it in LabVIEW8 and when I set the property node disabled = 2, I can't click on

the button. The only time I can click on the button is when I set disabled = 0

[Evan]

Which version of LabVIEW are you using?

I just tested it on 8.0 and during edit time I can change the value, which seems logical.  However, during run-time the button is truely disabled and clicking on it has not affect.

[AndrewAlford]

If you set the disabled/greyed out setting on the Boolean control the control does not allow user interaction while the VI is in run mode. The state of the control will change when the VI is in edit mode. I tried this in LV 7.1.1

Message Edited by AndrewAlford on 02-10-2006 01:43 PM

[RobCole]

A disabled button should not be functional. Unless you do something silly like in this VI (included).

     Rob

[tst]

I can't look at Rob's VI, and what I'm thinking of isn't "silly" (just usually very very unnecessary), but if you're using something like the Mouse Down event, it will be fired regardless of the control's state, because it only tells you if the mouse was clicked while over the control . An event which is affected is Value Change.

[winterishere8]

Bingo !

This was my mistake. Thanks a lot for your help and posts.

Now, I ve changed my event to "value change" rather than mouse down. Works perfect.