Hi!
You could in theory just download both the macros (CALLING and SUBMACRO) from post #31, and paste the magenta colored action from the CALLING macro as the first action of any macro you'd want to display an oscillating progress bar, indicating that it is currently running. But doing this into every macro will in practice probably cause having many overlapping instances where macros are calling this SUBMACRO simultaneously.
The way it is set up now the Semaphore Lock at the head of the SUBMACRO would prevent this by canceling any instance of the SUBMACRO being run on top itself, whilst also returning an error message. This error message can be turned off, by right clicking the semaphore lock and unselecting "Notify on Timeout". Then the first macro CALLING for an oscillating macro would get it, and any overlapping macros triggered after the first would not — first come first served.
I did however try here now disabling the Semaphore Lock completely, while having numerous macros run on top of each other, each CALLING for this progress bar. This also kind of worked, only sometimes displaying slightly glitching/blinking progress bar text when run on top itself. So after this test I am now thinking that the Semaphore Lock is not really necessary at all in this case.
If your macro is simply repeating, literary utilising the Repeat action, you can display a correctly calculated progress bar simply by right clicking the Repeat action selecting "Display Progress".
Display Progress
Other times it can also work to simply wrap all your actions in a Group action, right clicking and selecting "Display Progress" in this same way.
In other cases where you'd want to display a correctly calculated progress value, not simply displaying an oscillating bar, it can become allot more complex. In this case it might be better if you ask your question in a new thread, and I'd happily try to help you there. Because I do not as of now understand the behaviour you are explaining above, and imagine it quickly progressing into something outside this threads scope.
As this thread progressed it wound up being less about the progress bar and more and more about setting up the conditionals to give the behaviour of 'While Triggering Macro is executing'. This especially after I found a much simpler way of displaying an oscillating progress bar than the crazy mess I started out this thread with. For demonstrating purpose the oscillating progress bar just got along for the full ride of the thread, but the 'While Triggering Macro is executing'-behaviour have also proven useful for other situations. The solution from post #31 is however a perfect viable way of displaying a progress bar, and I use ut in a number of my macros.