cluster compatibility problem

[mpv]

Hi,

I want to upgrade a LabVIEW 7.1 vi to version 8.2, but I am having a big problem with the bundle and unbundle functions. These functions now have to use a cluster constant that defines the contents of the cluster. My problem is the very large size of the cluster, it contains about 64K of data of various types. This means the definition is huge, covering more than the size of a 19 inch screen. It also looks like this definition has to be repeated for each bundle/unbundle function, it is not enough to just wire it to the cluster at one place. I have also not been successful putting this clusterdefinition in a sub-vi. It looks like this syntax change makes the huge cluster all but unusable in version 8.2.
I could of course revert to a byte array, but I consider that a last resort.

Any ideas solving this problem, while retaining the cluster ?

regards, Matt

[Ben]

Post the cluster typedef along with some code illustrating the problem.

Ben

[mpv]

Hi Ben,

I found your answer about typdef clusters from another thread in december 2006, and I want to try that route, as it looks very promising.

Thanks for the answer, if I get stuck again, I'll be back.

regards, Matt

[Evan]

Matt,

Can you post a link to that thread in case someone has a similar issue to yours they can also find the solution.?

Thanks

[jjcimon]

I will try later  and reply, but what is my idea

JUST for the purpose of upgrade to 8.2 and store cluster!!

use this powerful web definition  for cluster  XML

1.  flattered to xml,  

2. copy the xml and paste to 8.2

3. unflattened to cluster,

I'll try and send you the vi if ok

can you just   create xml and save it, and send me the file?

jacques

[mpv]

Hi,

The thread that looks promising is:

http://forums.lavag.org/How-to-handle-changing-clusters-t5244.html&pid=20996&mode=threaded#entry2099...

specifically:

> 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 regards, Matt