LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Showing results for 
Search instead for 
Did you mean: 

Active Structure Debug Indication

Status: New

When entering debug mode (turn execution highlight on) it can be hard to see what is happening.


With event structures it can be hard, but there are subtile changes. Sometimes it's impossible. For instance, if you run this VI, and wait a while, it is impossible to why the VI has not stopped. In this case it's easy to deduce, but it can be really hard. Probes also don't provide a solution here...

Parallel Loops.png


SubVI's get a green arrow when they are executing. So, could structures get them as well?


Parallel Loops proposal.png

Knight of NI

Doesn't the wait itself get a green arrow?

LabVIEW Champion. It all comes together in GCentral GCentral
What does "Engineering Redefined" mean??
Knight of NI

Christian, that would not help in this exact example.  It is the Wait On Occurance that is holding it up.  So if that had the green arrows, we would be good to go.

There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Knight of NI

The "Pause ring"  might just do this already.  I need an example of why the pause ring does not help in well structured code to help me understand the idea.

"Should be" isn't "Is" -Jay
Proven Zealot

I like this idea. A lot.

Proven Zealot

This will be helpful. Kudos

Proven Zealot



>The "Pause ring"  might just do this already.


Do you mean pressing pause? In this case it does not do anything.


I agree, a lot of times you'd avoid the need for this (but it would still help). Normaly I'd avoid parallel loops inside a VI, but sometimes it's just called for. For instance, I recently put about 8 loops in parallel to handle 8 connections to the same TCP\IP device.


LabVIEW usually grays out stuff inside structures (in the exampe it does if you remove the structure), but in the posted example it does not. This could actually be a bug. Still the arrows would help to speed things up, you'd be able to tell what is going on in a blink of the eye.

Proven Zealot

I have one additional thought that keeps poping up. Since the idea is well received, I'll just through it in.


For event structures, we might want two color codes:


Green > the event structure is executing code inside it's structure (event is being handled).

Grey(?) > the event structure is active, but waiting for an event.


Actually, VI's could use a distinction like this as well:


Green > the VI instance is executing code inside.

Grey(?) > the VI instance is active, but waiting for another execution to finish (since the VI is not reentrant.


I first thought about orange (green, orange, red makes sense), but orange sugest some stress\panic, so grey might be better.

Proven Zealot

We are used to link  grey with disabled

Knight of NI
I mean the ring control that appears on the ribbon bar only when execution is paused.

"Should be" isn't "Is" -Jay
Proven Zealot

>We are used to link  grey with disabled


True. Perhaps orange is better. Or something else...


>mean the ring control that appears on the ribbon bar only when execution is paused.


The only thing that changes when execution is paused, is that some buttons in the ribbon bar are enabled. Most notibly, the step functions (step into, Step over, Finish). I don't get any ring control. (Could it be an add-on? Not sure if a provider can add a ring)


In the example, these stepping buttons are all disabled when pausing execution after a few seconds. This makes sense, since it cannot step over the wait for occurence function. So it's still not possible to see what is happening.