Progress bar in Structures

[RavensFan]

No No No.

If the "Some Code" case structure is the part that takes a long time to execute, your progress bar loop is not going to run until after that code is done running.  You have a data dependency between the long running case structure and the event structure.  Although the event will be triggered, the event structure won't execute until you've got the data coming out of case structure on that blue wire.

[DailyDose]

---

@VD89410 wrote:

Ah great, I forgot to put the divider outside. So it should be like:

Brilliance advice, thank you!

---

I don't understand what's "no brainer" about this.  Guessing from your comment "Some code," you plan to put the subVI that will be processed within that Case Structure.  If you were to put the all of your code in either the event structure or the case structure, then I would say, this is an 'acceptable' mock progress bar that fools the user into thinking there's progress.  Your For Loop should run in parallel with 'some code.'

[billko]

I was thinking you could set it up like a producer consumer logging loop, only instead of queuing a message to a logger after everything that merits a log update, you simply update the slider every time some "progress" has been made.