LV8.0.1 shared variable & coercion dot

[Zedd]

Hi all.

Within a LV 8.01 project at the moment I have variations of :

1) Strict Type definition (array of cluster)
2) Shared variable with data structure defined from strict type def (1)
2) Sub vi with same strict type def (1) as input.

I am currently seeing coercion dots on both the data sources (i.e shared var) output and sinks (sub vi inputs). A quick search of the forum showed similar problems having been seen before, but no solutions

Can this coercion dot be eradicated or do I have to live with it?

Matt

[chrisger]

hi there,

a strict typedef includes not only the data type but also the look of the control. since the shared variable only holds the data some information gets cut off, therefore you see a coercion dot.

similar behaviour can be seen with value - properties of control references of strict typedefs after a class cast to a non-strict class (but with same datatype).