How does it happen and how to prevent this: change of typ def cluster causes element miswired

[ergwser]

Hi all,

I have a big nested nested typ def cluster, several layers.  I use uncluster by name function to use it. 

Somehow changing the big typ def causes unlustered elements miswired. 

For example, element A was the unclustered element and used, then after I change the typ def, I don't remember how, may be delete some elements, maybe rename elements, then bacomes element B is the unlustered element and used.

It's very scary because it just happened automatically and no broken error reported and this may mess up the whole application.

Does this ever happen to anyone else? How to prevent it?

Thanks a lot for any help.

Anne

[Ben · Accepted solution]

Search on "Ben" "cluster" "type def" to see I have been bitten the same way.

THe earch will reveal the various things that have been suggested depending on which version of LV.

Ben's first rule of cluster

Avoid like the plague deleting elements or renaming them.

Other stuff:

If you have to delete an element, for change its representation to something that will break all instances e.g. change numeric to string. THen go fix all of the broken VI by tossing all refs to the field you want to delte. THen delete it.

in ealier version of LV it was better to have all of teh VIs that use that cluster open when the change is made.

In recent version NI has recomended edititng the cluster with all callers closed with the theory being that LV handles it better when opening the VI.

Since I follow "Ben's first rule of cluster" I don't run into the bug often with LV 2009.

Ben

[ergwser]

Thank you, Ben. You are always very helpful.