Loading bar

[J.Mamakos]

Scrap that. I now have a VI with two different versions of code. One version (the one that works) uses 128 past iterations of a shift register and 128 'build cluster' things. This looks rather unwieldy in code, though it's pretty basic. The other version was my attempt to use arrays and an extra For Loop to reduce the code size, but my brain can't be working cos i can't make it work as it should!

Please could someone point out the probably obvious mistakes i'm making here since i can't find them! 😞

[smercurio_fc]

Don't take this the wrong way, but frankly I think your approach is simply not practical and way too unwieldy (not to mention quite slow and not very responsive to clicking the Cancel button). Having a cluster of 128 (or whatever number) slides is, in my opinion, simply silly and I would really consider whether the effort is worth it. Yeah, a graduated color progress bar is pretty, but what's the point if it requires such complex and slow to respond code? Sometimes you have to deal with limitations of a language, and let's face it, LabVIEW 6.1 is really old.

[J.Mamakos]

Right. I have a working, simple progress bar which I am already using in my application in a couple of places and it works fine. However, I now have one (maybe two) other situations that require a slightly different execution of the progress bar.

The one I have at the moment (see attached) works from a FOR loop using the (N) terminal for its range and the (i) terminal for its fill percentage.

What I need now is a similar bar that works, not from a definite maximum as in a FOR loop's (N) terminal, but works off start and stop signals. I may well have to carry two notifications into the SubVI for this to work, and it will have to 'scroll' across much like those marquee things...!

Any ideas as to the easiest way to edit what I've already got to achieve this modification?

Thank you.

James

[J.Mamakos]

Coming back to this after modifying and editing code elsewhere, I find myself still unable to find a solution.

I want to create a marquee style loading bar that appears on a start signal, and goes away on a stop signal (both signals come from the calling VI). This would probably mean using notifiers or queues to 'transmit' the start and stop signals. The loading bar would also be modal so that nothing else can be pressed on the calling VI's FP. Therefore, an abort/cancel button may be useful for if something goes wrong (troubleshooting) or a get-out-of-here-quick situation arises.

Any ideas?

James