Fix bug where progress bar initialisation and updates were not correctly called in sequence either side of a scan/loop step function. This resulted in all updates to the progress bar being called after any functionality inside the step. So for longer running functions this would look like:
- The progress bar being initialised/displayed after the first iteration (i.e. delaying the display of the bar)
- Some updates being run directly after each other, causing some updates to look instant/jumpy
Thanks to @andrewlesak for spotting this!
Progress bars will now be updated in the correct sequence (with no API change):
- Bars will be displayed before the first iteration is computed
- Steps between updates be spaced appropriately
Contributors
andrewlesak