#4 jumping Progressbars

[Jan Hummel]

Hi!
The progressbars are not helpfull in giving an estimate for the processing time because they jump backward as soon as they reach the full 100%.

cheers,
Jan

[clochardM33]

Hi Jan,
I know what you mean, but that is not quite what they are doing.
They give you an estimate of the process time compared to the longest time in the process run.
The first run sets the final time for each of the three bars.
The next run uses this new maximum. Therfore the second (and thrid and fourth etc,) compare themselves to the first.

There are a couple of problems with them, but I couldn't come up with a better way to put something in the screen to show you that something is happening.
The process time (for any of the stages) is not predictable (but if you do the same thing twice you do get the same time). This means the very first time you process I don't know how long it is going to take. So I picked some time (I think it is 10s) and count up from zero to 10. If it gets to 10 and hasn't finished I give the bar a new maximum and count up towards it again. This continues until the processing stops. Now I know (approximately) how long this step takes so I can call this final time 100%. The next time you process something it counts up towards the 100% time.
This means that after the first run all three processes should finish neatly at the 100% time (for each process) keeping it pretty.

The recent release fixed a bug that accidentally reset the times so they didn't look as though they were doing anything.

clochardm33