Coercian dots

[Clint1000]

Is there any way to find out why you have a coercion in a type def??  I have a control type def with a number ( lots) of elements in it and an indicator type def.  I made a copy of the control type def  then changed it to an indicator.  When I connect the control to the indicator type defs I get a coercion dot.  The type defs are clusters of numbers, Booleans etc.

Thanks..

Can not post code. 

[aeastet]

You could create a control or constant from the VI that you are getting the coercion dot on. It should show you what format it is expecting. I am assuming that you know what you are feeding it.

[RavensFan · Accepted solution]

---

@Clint1000 wrote:

Is there any way to find out why you have a coercion in a type def??  I have a control type def with a number ( lots) of elements in it and an indicator type def.  I made a copy of the control type def  then changed it to an indicator.  When I connect the control to the indicator type defs I get a coercion dot.  The type defs are clusters of numbers, Booleans etc.

Thanks..

Can not post code. 

---

There must be something else going on there.  If you made a copy of a control and changed it to an indicator, it is such a straight lineage I don't see why there would be a coercion dot.

You probably have nothing to worry about.  But if you are still curious, attach the VI and the control file so others can look at it.

[Bob_Schor]

---

@RavensFan wrote:

---

@Clint1000 wrote:

Is there any way to find out why you have a coercion in a type def??  I have a control type def with a number ( lots) of elements in it and an indicator type def.  I made a copy of the control type def  then changed it to an indicator.  When I connect the control to the indicator type defs I get a coercion dot.  The type defs are clusters of numbers, Booleans etc.

Thanks..

Can not post code. 

---

You probably have nothing to worry about.  But if you are still curios, attach the VI and the control file so others can look at it.

---

You can always "change names to protect the innocent", i.e. make a copy of the TypeDef and change the element names to "I32-1, Dbl-1, String-1, ...".  This should still have the "coercion" problems you are worried about (though that seems strange, unless you, yourself, made a mistake when building the TypeDef, such as dropping a Numeric that you incorrectly assumed was an I32 when it was really a Dbl, or something like that).

Bob Schor

[Clint1000]

So there isn't anything like hovering my cursor over the dot and getting an explanation like you do when you have a broken wire?

Thanks.. 

[RavensFan]

You can hover over the wire and see the data structure in the context help window.

You can hover over the control and the indicator.

You'll have to do that and compare the differences in what is shown.

[billko]

Are you actually opening the typedef, copying the control that is inside, then pasting it somewhere else?  That's the only way I can see the created object having a coercion dot.

Edit: I think I misread something along the way.