Coerce Dot on a String

[tst]

Thanks Noah, that looks like useful information.

---

Ben wrote:

You have used some new terms that I have never heard prior.

---

That must mean you're not reading the nuggets!

The context help of the wire should provide a hint as to when this is happening:

[richjoh]

So from reading this post correctly, a typedef is a type that requires conversion, correct? Specifically, if I wire a typedef enum to the property node of a control, the coercion dot is expected due to LV conversion of typedef to U8? See attached pic. But the typedef is defined as U8 already, conversion still occurs? This is normal in LV 8.2?

If I wire a U8 constant the is no coercion as always. A U8 typdef wired to the property node needs conversion? Correct, please confirm?

Richjoh

[richjoh]

attached is below....

[tst]

The typedef is a different type (hence its name), so it requires a coercion, but as mentioned before, that doesn't always mean a data copy (see Noah's case B) above.

Incidentally, you're also using an enum, which probably will require a copy anyway, since it holds more data than the U8 itself.