Typedef "Value" Property Node issues to fix, please!

[X.]

As discussed here and here, it is annoying that a Value Property Node of a typedef is not typed properly (*).

Related or not, as discussed here, it is annoying that when you try to create a typedef constant for a typedef control, you have to actually do that from the Terminal. And the problem is compounded byt the fact that you cannot access the terminal from a Property Node! It is grayed out. A specificity of typedefs. All other Controls/Indicators terminals can be access by right-clicking any of their property nodes.

Thanks for reading.

Tested in LV 2011

(*) definitely not new in LV 2011

[X.]

First CAR still not fixed in LV 2012...

[X.]

Still well and alive in LV 2015...

[AristosQueue (NI)]

The CAR is marked as fixed in LV 2012.

I just verified in LV 2015. Works just fine.

[AristosQueue (NI)]

And the Find CAR appears to also be fixed. Also in 2012.

[X.]

You might well be right, but I am correct too.

Here is what I have on my diagram:

The local variable corresponds to the PN's control. Notice the red coercion dot.

1) If I force recompilation (Ctrl+ Run Arrow), nothing happens.

2) If I disconnect the local variable and try to reconnect it to the PN, nothing happens. I mean nothing. I CAN'T get a wire to connect the two.

3) If I Ctrl-Z all this, here is what I get:

No coercion dot. This VI has been recompitled dozens of time since I upgraded to 2015.

Edit: of course the control is a typedef.

[AristosQueue (NI)]

Works fine for me. I tried directly in 2015. I also tried creating a problem case in 2011 and then loading it in 2015. It mutates correctly.

I guess there must be something corrupt about your particular VI. Delete the control and re-drop it and see if the problem goes away.

----------------------