strict type def data blown out when updated

[aeastet]

I juat updated to 2012 and I saw that when I update a stryct type def of an enum type that it blew out all of my previous constants. I have arrays of empty arrys of enums. I know it did not do this before. I simply edited the list by removing an item save and applied the changes and now everythig is going.

Lots of extra work to go back and reset all of these.

[aeastet]

TO add to this. It seems that if I hit the rex X in the corner of the type def when closing before I have saved and applied. When it asked to save I say yes go back to my code and no more constants. This is the second time that I have had this problem today.

To many extra hours because of new bugs on old things!!!!!!

[Ben]

Quoting from My Type Def Nugget from march 2007 in the notes section

"

*** Type def’s define the data type and not the default values. You cannot use type def’s to establish default values. If you modify a type def that is used as constant on a diagram, all instances of that type def will be replaced with new instances. Default values that were saved in the block diagram will be lost when the constant is replaced with the new definition. This is by design. The method I suggest for establishing a default value is to use a sub-VI to explicitly define the value. In the case of clusters use a bundle by name node to set the fields as required.

...

Where I have illustrate the use of sub-VI’s to establish default values. In the example, there are two sets of default values of the type definition “Chan Info” (Channel Information) denoted by the green and grayed-out icons.

"

So...

I do not think it is a bug and is not new.

Frustrating?

Yes.

I use a sub-VI to establish the defaults. It adds another VI to the mix but it allows me to change it in one place instead of chasing down many and it also gives you a little documentation to explain what is what.

Ben

[aeastet]

Hey Ben thank you for your response. The problem I was having was not the values for the constants. I literally had to go through and replace every Strict Type def in my program to get it to work again. I do store the default values somewhere else.