How to handle changing clusters

[ErikHaverkamp]

Hi there,

Great forum, I stopped working with Labview at version 5.1 (when I was already happy with the UNDO feature). Now I started again and I am working in LabVIEW 7.1.

A question that I have already a long time is the following. For many applications I use one big cluster that contains many setting for let's say a certain application. I pass this cluster from one VI to another and then extract data from it or add data to it when necessary. However since this creates many VI's that have terminals IN and OUT for this cluster type I run into serious problems when I decide to change the cluster definition. If I change the cluster definition then I have to manually change this for all VI's that use the cluster. This is a very timeconsuming operation.

My question: is there a faster way to do it, or should I use another technique for keeping data together within an application?

Thank in advance,

Erik

[Grampa_of_Oliva_n_Eden]

Hi there,

Great forum, I stopped working with Labview at version 5.1 (when I was already happy with the UNDO feature). Now I started again and I am working in LabVIEW 7.1.

A question that I have already a long time is the following. For many applications I use one big cluster that contains many setting for let's say a certain application. I pass this cluster from one VI to another and then extract data from it or add data to it when necessary. However since this creates many VI's that have terminals IN and OUT for this cluster type I run into serious problems when I decide to change the cluster definition. If I change the cluster definition then I have to manually change this for all VI's that use the cluster. This is a very timeconsuming operation.

My question: is there a faster way to do it, or should I use another technique for keeping data together within an application?

Thank in advance,

Erik

Pop-up on your control and choose Customize.

Use the drop down to change change the control from a control to a typdef.

Save it.

replace all of the old occurnces with the typdef.

HINT:

After you create and save the edit it and add a new field. Save it.

This will break yur code every where the typdef is wired to a non-typdef'd control. Fix all the broken wires by replace the non-typedef with the typedef.

When you are done you will have found all of the places that need to be fixed (well maybe not all).

Ben

[syrus]

Pop-up on your control and choose Customize.

Use the drop down to change change the control from a control to a typdef.

Save it.

replace all of the old occurnces with the typdef.

HINT:

After you create and save the edit it and add a new field. Save it.

This will break yur code every where the typdef is wired to a non-typdef'd control. Fix all the broken wires by replace the non-typedef with the typedef.

When you are done you will have found all of the places that need to be fixed (well maybe not all).

Ben

In addition to this, if you only bundle and unbundle "by name" in your VIs, you will not break them unless you remove something from the cluster in the typedef.

[ErikHaverkamp]

Hello Syrus,

Thank you very much for the solution, I think this would have saved me a lot of time....

Thanks,

Erik :thumbup:

[Aristos Queue]

Since you're talking about changing clusters, you may be facing the problem of having data of your cluster flattened on to string and needing to unflatten it into your new cluster. The conversation in this thread may be useful.