Why this coercion dot on array indicator from strict typedef?

[cebailey]

Why is there a coercion dot on the second control?

I created a trivial 3 element array of doubles, and created an indicator by right clicking on it in the block diagram. That's the "CreateIndicator" control.

Then I did the same thing to create a second indicator on the same output wire, and from the front panel selected it and customized it to a strict typedef, saved, and applied changes. That's the "CreateIndicatorThenCustomize" control. It has a coercion dot on it, though. Why?

Thanks to anybody who can shed some light on this for me!

[Ben · Accepted solution]

Don't get me started on the "coercion dot = buffer copy" falicy (hm I think you just did!)

It that case LV is telling you there is conversion from non-type-defed to type-def'd that all.

Ben

[cebailey]

Thanks, Ben!

Seems weird that this would be considered a coercion. Why do they do it this way?

What is the falicy? Is it that you should avoid coercion dots because they force copies, and yet in this case there is no copying involved so the avoidance advice is incorrect?

Also, different question, why is Customize Control grayed out in the front panel Edit menu, as long as another control customization panel remains open from the previous use?

Finally, how did I miss this after all this time? Well, you probably don't know how I missed it. Actually, if you do know, it might be better to leave it unsaid anyway....

[Ben]

---

cebailey wrote:

Thanks, Ben!

Seems weird that this would be considered a coercion. Why do they do it this way?

Q1)

What is the falicy? Is it that you should avoid coercion dots because they force copies, and yet in this case there is no copying involved so the avoidance advice is incorrect?

Q2)

Also, different question, why is Customize Control grayed out in the front panel Edit menu, as long as another control customization panel remains open from the previous use?

Q3)

Finally, how did I miss this after all this time? Well, you probably don't know how I missed it. Actually, if you do know, it might be better to leave it unsaid anyway....

---

Q1 Correct!

Q2 Not being NI R&D I can only speculate that is was an expediant move to shut-down that functionality. It used to be possible to customize part of a control while customizing a control back in about LV 6. They shut it down making it more painful to do the edits within edits (you can save a control in one edit and then use "replace" to select it while editing the first)

Q3 I will leave taht question as an exercise for the reader.

take care,

Ben

[cebailey]

Thanks, as always, Ben.

I've played around with various ideas, and all the results are consistent with conversion to a typedef plus no other weird mechanisms apparent.