Do property nodes work correctly inside a VI marked as re-entrant?

[mpmurphy]

Using Labview 7.0, I ran into a problem after I marked a VI as reentrant. I narrowed the issue down to where I used a property node to look up the text that would appear in an input text ring control. Once the VI became reentant, the text could not be determined correctly. The attachments show a simplified example. "a_caller.vi" makes use of "a_subvi.vi". The sub VI simply passes the item selected on the input text ring control to an output text ring indicator. It also looks up the text itself and makes use of it by passing this text out too. This works as expected until "a_subvi.vi" is set to reentrant, at which time the output text ring is returned as the correct value, but the text is not.

Is this a bug?

[Odd_Modem]

I don't think it is a bug in 7.0. Front panels of reentrant vis do not show the information of each instance in 7.0 and the property node is displaying a default value of some sort. As a workaround you might try getting the strings[] property and using the ring value as an index into that array.

[Odd_Modem]

Just to follow up, you code method seems to work in 8.5 in both reentrant configurations.

[parthabe]

It happens as you said in LV 7.1 also.

But I think it is correect behaviour because a reentrant VI creates new instance of itself on the whole [meaning all the variables]. So the static property node becomes invalid or gets corrupted.

A workaround may be to pass the reference to the Ring from the Main VI into the Sub VI.

See the attached VIs in LV 7.0.

[Ben]

For LV 7.0 that behaviour is correct.

A work-around would use an enum and "format into string".

In LV 8 and latter, the behaviour of re-entrant VI's has been enhanced.

Ben

[parthabe]

---

@Ben wrote:

For LV 7.0 that behaviour is correct.

---

Ben,

Is the behaviour correct for LV 7.1 also ?

[Ben]

"

Is the behaviour correct for LV 7.1 also ?
"

I believe so.

Ben

[mpmurphy]

OK thanks for the suggestions