Changing the Property Node label does not update the Terminal/Control label?

[X.]

@Darin. K: I like the idea of a fused terminal/reference node. You should post that in the Idea Exchange.

@the others: Ouch! That hurts... Are you saying that this why I can't seem to keep any friend? 😉 (*)

(*) reference to "What about Bob?"'s scene in the pyschatrist office.

[Ben]

---

@X. wrote:

@Darin. K: I like the idea of a fused terminal/reference node. You should post that in the Idea Exchange.

@The others: Ouch! That hurts... Are you saying that this why I can't seem to keep any friend? 😉 (*)

(*) reference to "What about Bob?"'s scene in the pyschatrist office.

---

I was trying to pay you a compliment since the first thing required to recognize when something is wrong is to know what is right.

Ben

[Darin.K]

There is still fun to be had using the explicit PN and control reference:  Wire a Numeric control reference to a PN and choose 'Value'.  Disconnect and wire a string control reference to the PN.  Darn, no property is selected.  Delete the reference wire, now the Value property is selected and has the correct type, so go ahead and rewire the string reference.

[X.]

@Ben: 😉 is not :-). Sorry, I am no modern emoticon adept as some are on this forum (I won't name names :-).

[RavensFan]

---

@Darin.K wrote:

There is still fun to be had using the explicit PN and control reference:  Wire a Numeric control reference to a PN and choose 'Value'.  Disconnect and wire a string control reference to the PN.  Darn, no property is selected.  Delete the reference wire, now the Value property is selected and has the correct type, so go ahead and rewire the string reference.

---

You're right.  Same behavior as the implicitly linked property nodes.

Somehow the Value propety of the string is not considered the same class as the value property of a numeric or boolean.  (I haven't tried experimenting beyond these 3 datatypes.)

EDIT:  Okay I just tried an array of numerics vs. an array of strings.  No break there.

[Darin.K]

---

@Ravens Fan wrote:

---

@Darin.K wrote:

There is still fun to be had using the explicit PN and control reference:  Wire a Numeric control reference to a PN and choose 'Value'.  Disconnect and wire a string control reference to the PN.  Darn, no property is selected.  Delete the reference wire, now the Value property is selected and has the correct type, so go ahead and rewire the string reference.

---

You're right.  Same behavior as the implicitly linked property nodes.

---

Except you can actually make it switch in the explicit case.  In the implicit case you can only go back to the original control to make the value property reappear.  The explicit one changes upon disconnect of the reference wire.

[X.]

@Darin. K: can't seem to reproduce your symptoms (in LV 2011). I started with a Numeric reference to be able to access the Value property and then followed your explanations.

Here is what I get after connecting the String reference:

As Ravens Fan says, it mirrors the behavior I described above.

Now, and this becomes interesting (and seemingly different from what you are describing), if I delete the reference wire. here is what I get:

The Numeric Control is connected to a (apparently) String type value node and the wire is not broken!!! Gold...

(c) X 2012.

[Darin.K]

That is pretty sweet!  Try again without connecting anything to the value terminal, just wire the reference terminal.

[X.]

You mean like this:

(c) X 2012

[Darin.K]

LV10