Reference on different size of cluster broken

[Vincent90]

Type def the cluster let me show the same error ;

Wire : Class conflict

BR,

Vincent

[Vincent90]

The difference between our 2 instances are

i have "Include data type" checked, grayed and disabled. Can you see that as well when openning my project ?

Using control refnum does the mess ?

BR,

Vincent

[crossrulz]

I still don't have any of your VIs.  Your zip file just had the library file.

[Hooovahh]

---

@crossrulz wrote:

No.  You need to update it to have the same type as your data cluster.  This is where I am saying that you need to have a control type def.  That way when you want to add to the cluster later, you just need to update the type def.

Have a look at this code.  What I did is create a type def of the cluster I want.  I then made a couple of controls and indicators from it.  For the reference input on the subVI, I righ-clicked on it and selected "Show Control".  I deleted the cluster that was in there and dragged one of my type def clusters into the reference.  Now the reference type is tied to my type defined cluster.  Now when I go to add more elements to the cluster, it just works (once the VIs are saved due to the updated type def).

---

I typed up a big long response then realized I was wrong.  You can update the type def, but there exists a broken wire from the reference in the main, to the subVI.  If you delete the broken wire, and rewire it it works.  Is this a bug?

[Hooovahh]

Here is a video of what I was talking about.  I update the cluster, but the broken arrow exists, when I click on it the broken arrow goes away.  Also if you delete the wire and remake it all is good.

http://screencast.com/t/DO3wVSdfT

[Vincent90]

Hi,

I don't understand why after each zip, VI cannot be fin anymore...

Let's try this way :

I don't know if it a bug but it is hard to understand why it is not working...

BR,

Vincent

[crossrulz]

I just did a save on the VI and it was happy.  I agree that we likely have a bug here.

[Hooovahh · Accepted solution]

---

@Vincent90 wrote:

Hi,

I don't understand why after each zip, VI cannot be fin anymore...

Let's try this way :

I don't know if it a bug but it is hard to understand why it is not working...

---

Attatched is a quick update.  All I did was create a reference control from the typed control, and used that in the subVI.  Now all the controls and references are linked.  Update the type def, and resave the VI and it shouldn't be broken.

[crossrulz]

---

@Vincent90 wrote:

The difference between our 2 instances are

i have "Include data type" checked, grayed and disabled. Can you see that as well when openning my project ?

Using control refnum does the mess ?

BR,

Vincent

---

The major difference between our sets of code is the reference control on the subVI.  You didn't tie the reference type to the type definition.  It is still the generic "cluster".

[Vincent90]

<< You didn't tie the reference type to the type definition.  It is still the generic "cluster".>>

How to do this please?

Every time i create control from my property node, i always get that bad reference with "include data" gray.

When i take the reference you create it works fine, with the bug showed earlier, but saving the VI do the same thing as running it.

BR,

Vincent