The bars themselves only have a couple of important fields... total items and items completed. I'm not understanding all this other complexity you are specifying
The bars themselves only have a couple of important fields... total items and items completed. I'm not understanding all this other complexity you are specifying
Anything is better than a fake progress bar that turns into a static image as though it's frozen.
> Say the first 100 items on the list take 1ms except for the last item which takes 30s.
Yes, in your worst-case scenario, this would be the case - but when would that scenario occur. If each state of the progress bar represents a different operation (as in the gmail scenario), you can structure the different states in such a wy that this doesn't happen.
If different states represent different slices of same operation (e.g. copying files), it's not really likely that ine slice of the same operation always takes a disproportionate amount of time, compared to the other slices.