Why coercion dot on build array for XYGraph refnums?

[miguelc]

Anyone know why there are coercion dots in the attached .png? When I wire the first S11 Polar graph to the build array, there isn't a dot, but when I wire the second (S12 Polar) the coercion dot appears on the first. It wouldn't bother me too much except that the other polar plots ( the ones with Common in the title) are exactly the same and don't produce coercion dots on the build array.

Michael

[Ben]

All the elements of an array must be the same data type.

THere is something different about the one graph.

To find out more use the wire-tool help method that tst wrote about in this Nugget

http://forums.ni.com/ni/board/message?board.id=170&message.id=225321#M225321

And look very closely at the help window.

Ben

[miguelc]

Thanks Ben. I had already checked the wires, and I've attached an image of each wire for the 4 polar graphs that have coercion dots on the build array. As seen, the type is all the same: Waveform Graph Refnum (strict). Its the same type for the other four polar graphs (see first image) that don't have coercion dots on the build array. Could a property be set different for each graph? Could it be something to do with the strict type?

Michael 

Message Edited by miguelc on 03-02-2007 02:53 PM

[Ben]

When you float of the output array, what do you see?

Ben

[miguelc]

The output of the array is a 1D array of Waveform Graph Refnum (strict). See attached .png. You can see that the output of the two arrays is the same, but one has coercion dots on it. I figure this isn't a big deal, but it would be nice to know why this is happening.

Michael

[miguelc]

I think I figured it out. Looked a little closer at LV help (under index strictly typed refnums, control), turns out strict type definition of controls (in my case XY graphs) requires many things about the controls to be the same. These polar plots must have some properties that aren't compatible under the strict definition (a quick look didn't reveal anything, but I'm sure there's something different). The Build Array is coercing the top three refnums to the strict type definition of the bottom refnum,  which is why it says 1D array of S22 Polar (Waveform Datatype Refnum(strict)), they are all of the type S22 Polar now. Now I have to see if the Property Nodes will still behave as expected.

I guess if they don't II could use a To More Generic Class function on each of these VI Server references, kind of annoying but I guess that would work...

Thanks for your help Ben.

Michael

Message Edited by miguelc on 03-02-2007 04:06 PM

[Ben]

"To More [Specific] Class function " when it comes time to use them.

Yep, you are way ahead of me.

Ben