PanelBounds vs "Panel Bounds" Is this a bug?

[Neil.Pate]

Hi all,

Attached is a VI which basically sums up an oddity I am seeing. This is LV 8.6.1 so it may have been noticed/corrected by now, just want to see.

If I drop a FP.PanelBounds property node, I get slightly different typedef if I create a constant depending on whether the node is configured to write or read.

The differences are quite subtle, the text has different capitilisation and the name of the cluster is also different.

Is this a bug?

Sorry for the big VI attached, I did not really have time to do a more efficient (graphically) version.

[Owen.S · Accepted solution]

Hi nrp,

I can see this behaviour in LV 2009 SP1 and could not find any outstanding CAR's. I have filed a CAR with number #234695.

Thanks for pointing this out.

 Kind regards,

[RavensFan]

Interesting.  And if you wire the output of one property node to the input of the other, you don't see any coercion dot because of the differences in the typedef.

Image for those who can't open the VI.

Message Edited by Ravens Fan on 06-11-2010 11:17 AM