Cluster typedef doesn't update correctly

Question

Hello everyone,
I am new to using typedef controls so i'm hoping that I just overlooked something simple.  I am using a cluster typedef control in Labview 8.6 consisting of enumerated controls and a few numeric controls.  I've noticed that when I change the typedef cluster, it does not update properly on the VI in which it is used.  A specific example, which has been driving me crazy:
I decided that I need to change one enumerated control within the cluster so it's name is more descriptive and it has more options.  So i open the typedef control, change the name, and add two items through edit items... Save and Close.
Now, when I open the main VI that I use, I see that the name of the enumerated control has updated, but the new list items are missing.  Since Auto-update is selected, I can't click Apply Changes, since they were technically already updated.  To get around this I have to delete the typedef control and add it back in.
Since the name is updating, I know that it is linked properly.  Did I do something wrong when making the typedef control?  I've attached the control itself, although I doubt this will help.
Thanks.
Solved!
Go to Solution.
Attachments:
cluster_typedef.ctl ‏6 KB

Answer 1

I'd like to push this up to the labview dev folks and ask why could a string outputing version of an enum not be created and functional as a type def. I understand the difference between enums an rings. But I would like to suggest that the powers that be create a data type version for strings similar to the enum which updates all instances of a type def when changes are made to the string content within. 
To draw a parallel. An enum pairs the string label with a number and packages the two as part of the type def. Instead could we not pair the string label with a string and again package the two as a type def? You could choose to have the label and string content match or not as needed but the pair would update universally.
Here is one instance where this would be useful. I have been using the Asynchronous Message Communication Library lately which utilizes the standard Labview queue funcitons. While the standard queue functions can accept various data types the AMC library is limited to string messages only and rewriting the entire AMC lib is time prehibitive. 
So it would be very convienent to have something that looks like a combo box constant as a type def to feed into the AMC libraries instead of individual string constants. It would significantly reduce errors when repeatedly typing the same sting constants repeatedly only to find them the hard way after hours of debug.