10-13-2009 03:39 AM
Hi, In Labview version 9.0 (32-bit) there seems to be a conflict between help info for the Enum constant as applied to the disable property node . If I right click on a control variable and select create-> property node -> disable. If I then right click on disable -> help for disable, the help lists the following interger assignment 0 - Disable, 1- Disable and Greyed, 2 Enable. If however, I right click on the generated Enum constant and select properties -> Edit Items, the listing order is as follows; 0- Enable, 1- Disable, 2- Disable and Greyed. The latter assignment is how the Enum constant actually works. It appears that the help information may be incorrect.
Regards,
Pat
Solved! Go to Solution.
10-13-2009 03:45 AM - edited 10-13-2009 03:45 AM
I think this is a good catch.
Can you post a snapshot of this bug?
10-13-2009 04:55 AM
Hi,
I compared it with 8.2.
In 8.2 creating a constant, indicator or control by right clicking on the "disabled" property node gave an object of type U8, which operates in accordance with the "help for disabled", ie
0=Enable
1=Disable
2=Disable/grey
In 9.0/2009 right clicking and creating on the property node gives an Enum (of datatype U8) with names/values in agreement with 8.2, and operation as in 8.2, BUT the "help for disabled" message says
0=Disable
1=Disable/grey
2=Enable
Thus I would agree that this is a documentation error, and the LabVIEW is correct.
N.I. Can we have a CAR please?
P.S. I do think that it is a good idea to have made the disabled property an enum, whilst maintaining compatability with previous code. I always wondered why it wasn't that way in earlier revisions.
10-14-2009 04:47 AM
Hi Pat,
Good find on the error. A CAR already exists for this and is currently being worked on. The help documentation is in fact incorrect and until this is fixed use 0 - Enabled, 1 - Disabled and 2 - Disabled and Greyed out.
Regards,
Jas.W
10-14-2009 06:01 AM
Dear Jason,
Can you please post the CAR # here for reference.
Thanks,
Mathan
10-14-2009 06:58 AM