Bug Report: lv2010; Inconsistent value returned from sub-vi Example included

[Michael.Proctor]

I would think that this has all the qualities of a bug and not a wolf cry

as the behaviour remained even with a good dose of rewrite of the vi

and also swapping the positions of the Terminal with the local variable eliminated the inconsistent behaviour.

michael

[Ben]

---

@Michael.Proctor wrote:

I would think that this has all the qualities of a bug and not a wolf cry

as the behaviour remained even with a good dose of rewrite of the vi

and also swapping the positions of the Terminal with the local variable eliminated the inconsistent behaviour.

michael

---

After years of reporting and logging LV bugs, I have found that even after a CAR (Corrective Action Report) is filled R&D may come back and tell me they fixed a bug and the new behaviour is correct.

So we have to wait and see.

Ben

[RavensFan]

---

@Ben wrote:

Sorry I don't recall that bug.

Thank you,

Ben

---

I'm not saying that previous thread was a bug, just something about having a terminal in case structure cause a difference in behavior of the subVI that the LabVIEW programmer wouldn't be expecting.

Maybe it was a matter of an indicator terminal that did not execute would return its default value vs. a value from a previous run of the subVI when the terminal may have been executed.

Something I thought I read in the past that I can't remember any details on, and I just am not getting the right search terms together to find it again.

[Darin.K]

Perhaps you are referring to the "Clear as Mud" post?

[RavensFan]

---

@Darin.K wrote:

Perhaps you are referring to the "Clear as Mud" post?

---

That may be it.  I had read it before.  I'll have to read it again to see if it is it.

I did find another thread that seems to be related to the issues in this thread, particularly read messag3 4.  I am sure this isn't the one I was looking for because it was marked as "new" to me, and was posted a couple years before I started working with LabVIEW and participated on the forums.

http://forums.ni.com/t5/LabVIEW/Local-variable-behaviour-different-with-panel-open/m-p/81012#M49675

[Darin.K]

It is not exactly related, but I never get tired of that post.

Could be some optimization new to LV10 having unintended consequences.

[charris · Accepted solution]

---

@Ben wrote:

Hi Micahel,

I am slow to say bug because "boy who cried wolf" but based on Bill's gut feel, I have requested an App Engineer follow-up. It may take a couple of days for them to complete the work, so standby.

Thank you,

Ben

---

I've confirmed the symptoms in LV 2010 and 2009, and agree that this is definitely not expected behavior. I've catalogged and submitted it to R&D under CAR# 256324.

FYI, confirmed the behavior in Windows 7 x64 on 32-bit LV 2009 and 2010.