highlight of subVI not shown LV2010

[richjoh]

In Labview 2010 (andy maybe 2009) the green highlight RUN arrow does not identify a running subVI from the top-level VI's block diagram (BD) when you click on highlight (light bulb icon). I confirm this works just fine in LV8.6.

Recreate this by running a subVI inside a top-level VI using while loops in each. Subsequently turn on highlight debugging and LV2010 does not show the the green run arrow over the running subVI. LV8.6 works just fine.

Thought I throw this up since I've spent considerable time looking for why my new code just stop and initially I'm able to determine the current run location in the code.

Attached are LV2010 and LV8.6 VIs that show the issue. These attached VI do nothing and its just to demonstrate the issue... when you click highlight icon.

[Christian Mergl]

LV2010 f2

Btw, to wire the stop into the SubVI doesn't stop your VI.

[RavensFan · Accepted solution]

I think the question comes down to when you press the highlight button.  I looked at your LV8.6 version in LV9.  If I start the VI, then press the highlight execution button, I don't see a green arrow on the subVI.  If I press the highlight button before starting the main VI, I see the green arrow on the subVI when it gets to it.  If I unclick highlight execution, the green arrow goes away, but comes back when I turn on highlighting again.

So it seems whether the green arrow shows depends on whether highlight execution is on when the subVI is first entered.

I think the behavior as changed, possibly between LV 8.6 and LV9.  When I back saved your VI's and ran them on LV8.5 (I don't have 8.6 installed anywhere to check this right now), the green arrow will always show up on highlight execution.  Personally, this is the behavior I prefer.  I would like to have the green arrow show even if I turn on highlighting after the subVI is entered.  That way you know where you code may be stuck.

Perhaps someone with NI can comment on the behavior of the green arrow with highlight execution and confirm whether the behavior has changed.  It seems to me it has, and not for the better.  I would even go so far as to suggest this is a bug that was introduced in LV9.

[Christian Mergl]

That's right.

When you start the VI first, then turn on highlight execution the green arrow doesn't show up.

This is allready reported to RnD with CAR#192200

Christian

[richjoh]

Installed Labview 2010 SP1 (aka Suite 2011 DS1) today and the problem still persist. Hope this get addressed sooner than later.

[RavensFan]

Any word whether this bug was fixed in LV 2011?

I looked in the bug fix list and did not see it mentioned.  http://zone.ni.com/devzone/cda/tut/p/id/13257

This is an important bug to be fixed.  If I am running an application, and I go through my exit routines to shut it down, but it fails to shutdown promptly, I want to go to highlight execution so I can see which of my subVI's are still executing and figure out why they are hung up.  Without the green arrow on the subVI, it is difficult to figure out where to start looking.  I don't want to turn on highlight execution beforehand just to see the green arrow because it would take too long for the exit routines to run, and there is no guarantee whatever bug I have will manifest itself during that particular exit sequence.

[Patricia B]

Hello,

I checked the status of the CAR and it has been documented as fixed in LV 2011. I tried it out myself in 2011 and verified the correct behavior. Below is a link to download 2011 if you would like to it out as well.

http://www.ni.com/trylabview/

Best,

Patricia B.

[RavensFan]

Thanks, Patricia.

That is good news.  I should be getting my LV 2011 discs anytime now.

I just didn't see that CAR# listed in the bug fix list above or in the Readme.

Is there any reason it wouldn't show up in those lists?

[Jon_S.]

Hello Ravens Fan,

When the bug fix list is compiled we have a query that searches for fixed CARs that have certain criteria.  One of the criteria that we look for is where it was found.  This bug was first discovered in house by a devleoper so it wasn't marked as found by a customer.  When this forum post was created the AE should have updated the CAR to link to the service request that was automatically created.  If one of these two fields were marked our query would have pulled in this CAR.

This is the reason that we mention the list isn't exhaustive.  We try to list every CAR that a customer has reported or encountered but sometimes they can slip through the cracks.

[RavensFan]

Thanks, Jon.

That makes sense.

-Bill